Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f9b2ead23d50f029d821082e2883e22534ddab06e3cdcc496836870906e3f298

Tx prefix hash: 2be72198889dfc8eae3f5b5151e92d97f8f270523e4c0d74dad957368fe408b5
Tx public key: 5ade3e2fe3cd336d79c1ae6f760f8d07cf12b67cfd22b3c4382ab76a5a2d2897
Timestamp: 1738673163 Timestamp [UCT]: 2025-02-04 12:46:03 Age [y:d:h:m:s]: 00:289:09:41:17
Block: 1211930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204600 RingCT/type: yes/0
Extra: 015ade3e2fe3cd336d79c1ae6f760f8d07cf12b67cfd22b3c4382ab76a5a2d28970211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb6b38a304143fb67b7bf174c86e0bfe05674deb1b6b50b0e342d0cebe310a98 0.600000000000 1698697 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1211940, "vin": [ { "gen": { "height": 1211930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb6b38a304143fb67b7bf174c86e0bfe05674deb1b6b50b0e342d0cebe310a98" } } ], "extra": [ 1, 90, 222, 62, 47, 227, 205, 51, 109, 121, 193, 174, 111, 118, 15, 141, 7, 207, 18, 182, 124, 253, 34, 179, 196, 56, 42, 183, 106, 90, 45, 40, 151, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8