Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 830c7ef86de097fb094621185af10e3c1ad5c336edd14cb2b7001f1d1be0b2e5

Tx prefix hash: 9c0715be14fb5391a56455be2f57ba3f6398ee0c372760aa018c8f11912d8794
Tx public key: da1cbfeafff8b41607e5b9116814f3dd365cfe78930d75ecd0f6629c9d035b84
Timestamp: 1730638643 Timestamp [UCT]: 2024-11-03 12:57:23 Age [y:d:h:m:s]: 00:020:16:08:37
Block: 1145674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14792 RingCT/type: yes/0
Extra: 01da1cbfeafff8b41607e5b9116814f3dd365cfe78930d75ecd0f6629c9d035b840211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fde7ce0d88f837a407528c3d6bf2b9e1a9c4824cb058c22ff368969b1781eac 0.600000000000 1630163 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": 1145684, "vin": [ { "gen": { "height": 1145674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fde7ce0d88f837a407528c3d6bf2b9e1a9c4824cb058c22ff368969b1781eac" } } ], "extra": [ 1, 218, 28, 191, 234, 255, 248, 180, 22, 7, 229, 185, 17, 104, 20, 243, 221, 54, 92, 254, 120, 147, 13, 117, 236, 208, 246, 98, 156, 157, 3, 91, 132, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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