Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad2a9c75e3dae3e7391d1d2d469951b532765824e57c8c57ba92175c1c9a3ec

Tx prefix hash: 22e1c523f35f0e9c1fb8cb1aabc92cdc3cdd9a2def94c4a6fa9d3388d7fb8cfd
Tx public key: abf057fb7cae53e2eee30ac992d528b4837d15bacf2f96d05979f7153fe2f53d
Timestamp: 1712821897 Timestamp [UCT]: 2024-04-11 07:51:37 Age [y:d:h:m:s]: 01:203:22:25:16
Block: 998016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404460 RingCT/type: yes/0
Extra: 01abf057fb7cae53e2eee30ac992d528b4837d15bacf2f96d05979f7153fe2f53d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e73155032ea06c8f2c16d693864c368853a707574f70df086a5298db05ee6888 0.600000000000 1458450 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": 998026, "vin": [ { "gen": { "height": 998016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e73155032ea06c8f2c16d693864c368853a707574f70df086a5298db05ee6888" } } ], "extra": [ 1, 171, 240, 87, 251, 124, 174, 83, 226, 238, 227, 10, 201, 146, 213, 40, 180, 131, 125, 21, 186, 207, 47, 150, 208, 89, 121, 247, 21, 63, 226, 245, 61, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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