Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e458c1ca837535706d1719b8049df074aef5066aaced6ca7da052fb5b1dd64ae

Tx prefix hash: 68f49544f827c03e0d7af73268842369ec0fa08ec8201d1848a2d8b8685b934d
Tx public key: ced06f038e5632597e7164e28e714b9d11b823e038c26ac0d029eb88470ee884
Timestamp: 1721906764 Timestamp [UCT]: 2024-07-25 11:26:04 Age [y:d:h:m:s]: 01:106:20:16:37
Block: 1073359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334860 RingCT/type: yes/0
Extra: 01ced06f038e5632597e7164e28e714b9d11b823e038c26ac0d029eb88470ee88402110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0107fcf87d819a19921f11de865992c9a90a7a5a437283a352c0021942f1aa2 0.600000000000 1545860 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": 1073369, "vin": [ { "gen": { "height": 1073359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0107fcf87d819a19921f11de865992c9a90a7a5a437283a352c0021942f1aa2" } } ], "extra": [ 1, 206, 208, 111, 3, 142, 86, 50, 89, 126, 113, 100, 226, 142, 113, 75, 157, 17, 184, 35, 224, 56, 194, 106, 192, 208, 41, 235, 136, 71, 14, 232, 132, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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