Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07df9fdec67dfe6ff4daca21c0e188b8a4d51d0d87cc6b0944953873a1c8ee60

Tx prefix hash: 70f42a0e09bc470da99167b62ba6bc7d6684cfff11cabf96c9c2226637a69f35
Tx public key: 8c4ce5d4e7825f145838c0a90239bdb09700a53b583cc3752b946858e3743be3
Timestamp: 1764411272 Timestamp [UCT]: 2025-11-29 10:14:32 Age [y:d:h:m:s]: 00:022:18:48:08
Block: 1422627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16306 RingCT/type: yes/0
Extra: 018c4ce5d4e7825f145838c0a90239bdb09700a53b583cc3752b946858e3743be302110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9a7c06d8c59a6b9e0df1ac7833b8ccf3c72d8aeab536c8a1016799f1b2613d1 0.600000000000 1911196 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": 1422637, "vin": [ { "gen": { "height": 1422627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9a7c06d8c59a6b9e0df1ac7833b8ccf3c72d8aeab536c8a1016799f1b2613d1" } } ], "extra": [ 1, 140, 76, 229, 212, 231, 130, 95, 20, 88, 56, 192, 169, 2, 57, 189, 176, 151, 0, 165, 59, 88, 60, 195, 117, 43, 148, 104, 88, 227, 116, 59, 227, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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