Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5cd3451bcfe8553db377177a62b06e58c9fada161e84785333686942cfd87e1

Tx prefix hash: ad4c636ea051f6342513550b5bdb54a547a5ebcb2c2ec2a00b0f9821cbf6e1a8
Tx public key: 0aa69af5d9cb667d6b7b0e8ca9220d7e6c05d3826fcffb08eb0092649b536b59
Timestamp: 1718360283 Timestamp [UCT]: 2024-06-14 10:18:03 Age [y:d:h:m:s]: 00:208:06:40:45
Block: 1043972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149039 RingCT/type: yes/0
Extra: 010aa69af5d9cb667d6b7b0e8ca9220d7e6c05d3826fcffb08eb0092649b536b590211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 583db31084fc38514e0e171c48ddb9651cee8adf22eb1c708696a1c06f5e05e3 0.600000000000 1513153 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": 1043982, "vin": [ { "gen": { "height": 1043972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "583db31084fc38514e0e171c48ddb9651cee8adf22eb1c708696a1c06f5e05e3" } } ], "extra": [ 1, 10, 166, 154, 245, 217, 203, 102, 125, 107, 123, 14, 140, 169, 34, 13, 126, 108, 5, 211, 130, 111, 207, 251, 8, 235, 0, 146, 100, 155, 83, 107, 89, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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