Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60406528686800cd971f07f42308d5109fe22b6e621ea073f9d46951f5f6c1cd

Tx prefix hash: 3db31c9c000394374a17aea0f6147b4f45974d55f7f9ee9e964f706bc7d02718
Tx public key: dd33d7d34f5b38b674089c843a026026e7acab6b925aec66c9fa7674dd161ecd
Timestamp: 1766181701 Timestamp [UCT]: 2025-12-19 22:01:41 Age [y:d:h:m:s]: 00:004:02:04:48
Block: 1437288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2912 RingCT/type: yes/0
Extra: 01dd33d7d34f5b38b674089c843a026026e7acab6b925aec66c9fa7674dd161ecd0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 312492ee23fb4e08da9c5e7f36423603fe838eae975bddae860acd5902239fc5 0.600000000000 1926095 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": 1437298, "vin": [ { "gen": { "height": 1437288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "312492ee23fb4e08da9c5e7f36423603fe838eae975bddae860acd5902239fc5" } } ], "extra": [ 1, 221, 51, 215, 211, 79, 91, 56, 182, 116, 8, 156, 132, 58, 2, 96, 38, 231, 172, 171, 107, 146, 90, 236, 102, 201, 250, 118, 116, 221, 22, 30, 205, 2, 17, 0, 0, 0, 1, 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