Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d5cf70d50b9d5af631932809e30b3146e36a2c86095503ca5942e7b50c623cd

Tx prefix hash: 076b4a8b664ec218c5e07cf5b34d0277f4f63d729132a08e27bf951d05457a90
Tx public key: 612a6a691ff8b04cd1ab3600eb566b88660f96ab1d548504b58627c2f73f9fcd
Timestamp: 1764021096 Timestamp [UCT]: 2025-11-24 21:51:36 Age [y:d:h:m:s]: 00:044:09:00:29
Block: 1419384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31781 RingCT/type: yes/0
Extra: 01612a6a691ff8b04cd1ab3600eb566b88660f96ab1d548504b58627c2f73f9fcd0211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f0e62219a03519d01e8972fd247c6518edbe1f035c5621d384ca5e749a25968 0.600000000000 1907921 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": 1419394, "vin": [ { "gen": { "height": 1419384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f0e62219a03519d01e8972fd247c6518edbe1f035c5621d384ca5e749a25968" } } ], "extra": [ 1, 97, 42, 106, 105, 31, 248, 176, 76, 209, 171, 54, 0, 235, 86, 107, 136, 102, 15, 150, 171, 29, 84, 133, 4, 181, 134, 39, 194, 247, 63, 159, 205, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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