Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 764a2d2b6e774399e36de73b6b1e9c872ef65ef56040030b5a7bb863865b0dfb

Tx prefix hash: a558d44d2fcb00e602919ab5f38cb103b21b031516bec99701e356e0afd00da5
Tx public key: f51bef9343deb7d7a3a65e5e2f1c138b5fb9ea62ccd4dc3360bf38d3a0213494
Timestamp: 1722036388 Timestamp [UCT]: 2024-07-26 23:26:28 Age [y:d:h:m:s]: 01:104:20:37:28
Block: 1074430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333441 RingCT/type: yes/0
Extra: 01f51bef9343deb7d7a3a65e5e2f1c138b5fb9ea62ccd4dc3360bf38d3a021349402110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 024b351fa6fbc76b3a6cd8fc3c4392b2a75bc269a204c5f03ac745a06ea57ff7 0.600000000000 1546943 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": 1074440, "vin": [ { "gen": { "height": 1074430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "024b351fa6fbc76b3a6cd8fc3c4392b2a75bc269a204c5f03ac745a06ea57ff7" } } ], "extra": [ 1, 245, 27, 239, 147, 67, 222, 183, 215, 163, 166, 94, 94, 47, 28, 19, 139, 95, 185, 234, 98, 204, 212, 220, 51, 96, 191, 56, 211, 160, 33, 52, 148, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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