Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1f6e51b29580dd276bc4b6f2f42f265711ccf84de74f659b8dcdbc5933eb422

Tx prefix hash: 8ebbdbdbb7ec6b9a4e81ea23b311dd78eb3bffc486db18b8243f587796934828
Tx public key: cc17f0bda36ba15ee44a786c34cc2ce95ae0265d336c73919683a0e33e2e4781
Timestamp: 1762579729 Timestamp [UCT]: 2025-11-08 05:28:49 Age [y:d:h:m:s]: 00:085:06:27:08
Block: 1407443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60864 RingCT/type: yes/0
Extra: 01cc17f0bda36ba15ee44a786c34cc2ce95ae0265d336c73919683a0e33e2e47810211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c305f9ae98a3923b6204066d1d07e8f7a883f0e4a0cfdf31275d36cfcf31adb 0.600000000000 1895864 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": 1407453, "vin": [ { "gen": { "height": 1407443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c305f9ae98a3923b6204066d1d07e8f7a883f0e4a0cfdf31275d36cfcf31adb" } } ], "extra": [ 1, 204, 23, 240, 189, 163, 107, 161, 94, 228, 74, 120, 108, 52, 204, 44, 233, 90, 224, 38, 93, 51, 108, 115, 145, 150, 131, 160, 227, 62, 46, 71, 129, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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