Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0e3a38a15d70baad53fcbf698894a7df9a34c11534a98add0af72ad9e37a198

Tx prefix hash: ffb83ed6d4b83483df6814166086328f4779febf02190917cb4a5206352e2b3e
Tx public key: 0060abc3c8a08f9254ad5ddf5cfd7d7fa1faae41dd8fbf21cffa5b419239dd4a
Timestamp: 1735174567 Timestamp [UCT]: 2024-12-26 00:56:07 Age [y:d:h:m:s]: 00:330:08:35:28
Block: 1183239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233615 RingCT/type: yes/0
Extra: 010060abc3c8a08f9254ad5ddf5cfd7d7fa1faae41dd8fbf21cffa5b419239dd4a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 642c3d731f4ac6e67fff3bde1552e8e78453222f3fd1a8ac0328529e2f20eed9 0.600000000000 1669680 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": 1183249, "vin": [ { "gen": { "height": 1183239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642c3d731f4ac6e67fff3bde1552e8e78453222f3fd1a8ac0328529e2f20eed9" } } ], "extra": [ 1, 0, 96, 171, 195, 200, 160, 143, 146, 84, 173, 93, 223, 92, 253, 125, 127, 161, 250, 174, 65, 221, 143, 191, 33, 207, 250, 91, 65, 146, 57, 221, 74, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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