Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018e53e1fd3f5a2640e2b4a6333221ba5ccbb77a36fb7646215e4d7cda4c50e5

Tx prefix hash: eb3c76c562be34966c325a7740cc604b3bcfcfeef609bd0856eff66852841de5
Tx public key: 693967a899520b7f60cce4d24ce48e527e1a1e6b94c844cbee01f7b6821f379a
Timestamp: 1732902663 Timestamp [UCT]: 2024-11-29 17:51:03 Age [y:d:h:m:s]: 00:115:15:42:30
Block: 1164429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82453 RingCT/type: yes/0
Extra: 01693967a899520b7f60cce4d24ce48e527e1a1e6b94c844cbee01f7b6821f379a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7324378fb88cee7b86d5dfad91dcac1dda6c9bab05d9e29f49905787a9b41649 0.600000000000 1650102 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": 1164439, "vin": [ { "gen": { "height": 1164429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7324378fb88cee7b86d5dfad91dcac1dda6c9bab05d9e29f49905787a9b41649" } } ], "extra": [ 1, 105, 57, 103, 168, 153, 82, 11, 127, 96, 204, 228, 210, 76, 228, 142, 82, 126, 26, 30, 107, 148, 200, 68, 203, 238, 1, 247, 182, 130, 31, 55, 154, 2, 17, 0, 0, 0, 3, 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