Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46f4a6d5b1dbfdcd6214c0543b18541ff95d0d983eee1bc0226058cc39da091a

Tx prefix hash: 7f86955c8dfe4a84c20c28bbd2d31aea3f96edb5b69adf3ff2aaf5540b47fa97
Tx public key: f914c4f66d2b946a2623b537560dfe49e404d876c1467143bd8da0e92cf82102
Timestamp: 1765983809 Timestamp [UCT]: 2025-12-17 15:03:29 Age [y:d:h:m:s]: 00:004:21:44:46
Block: 1435645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3514 RingCT/type: yes/0
Extra: 01f914c4f66d2b946a2623b537560dfe49e404d876c1467143bd8da0e92cf821020211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3459b2d13ddc4cfb76629e196b729c88af26ebc5c753600191f5b8c86235b9d 0.600000000000 1924442 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": 1435655, "vin": [ { "gen": { "height": 1435645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3459b2d13ddc4cfb76629e196b729c88af26ebc5c753600191f5b8c86235b9d" } } ], "extra": [ 1, 249, 20, 196, 246, 109, 43, 148, 106, 38, 35, 181, 55, 86, 13, 254, 73, 228, 4, 216, 118, 193, 70, 113, 67, 189, 141, 160, 233, 44, 248, 33, 2, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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