Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d396c80f05d6814ca10fb2d0fe348e9b8e9cc579fcb8e718c3cdcab2ba1902

Tx prefix hash: 532ee72303335f9d962c925d4f9c5a1ad1e8abd2684bc58e7ca79ce4fa610c1a
Tx public key: 1d1f1b6fe7a8899080a4831ee978a16aa46e7bb9915454ec64373a4c0e0d0bcb
Timestamp: 1757424594 Timestamp [UCT]: 2025-09-09 13:29:54 Age [y:d:h:m:s]: 00:135:14:45:41
Block: 1364746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96934 RingCT/type: yes/0
Extra: 011d1f1b6fe7a8899080a4831ee978a16aa46e7bb9915454ec64373a4c0e0d0bcb021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 628b0c2a8478f5675a79147d6e4cddf8e5cc860a45592711c814a176a589d134 0.600000000000 1852785 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": 1364756, "vin": [ { "gen": { "height": 1364746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "628b0c2a8478f5675a79147d6e4cddf8e5cc860a45592711c814a176a589d134" } } ], "extra": [ 1, 29, 31, 27, 111, 231, 168, 137, 144, 128, 164, 131, 30, 233, 120, 161, 106, 164, 110, 123, 185, 145, 84, 84, 236, 100, 55, 58, 76, 14, 13, 11, 203, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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