Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6429c86027518ed79659315abec630cdb65c5c8c5bf147acbe346bb019bd265c

Tx prefix hash: cf86c93924cd30b909cbcfe7d4851fe498d3c8905c83fd1fbaada9f355c909c9
Tx public key: 5b3bec3d04d247a7dd32d51e5487f982141f1a00373d4a16fd36e3754c73d09b
Timestamp: 1717799790 Timestamp [UCT]: 2024-06-07 22:36:30 Age [y:d:h:m:s]: 00:145:08:43:25
Block: 1039311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104054 RingCT/type: yes/0
Extra: 015b3bec3d04d247a7dd32d51e5487f982141f1a00373d4a16fd36e3754c73d09b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8565a949aa9b41768718c92d9ccc26a44e75a17412db12194f571c015ea5c8c8 0.600000000000 1507944 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": 1039321, "vin": [ { "gen": { "height": 1039311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8565a949aa9b41768718c92d9ccc26a44e75a17412db12194f571c015ea5c8c8" } } ], "extra": [ 1, 91, 59, 236, 61, 4, 210, 71, 167, 221, 50, 213, 30, 84, 135, 249, 130, 20, 31, 26, 0, 55, 61, 74, 22, 253, 54, 227, 117, 76, 115, 208, 155, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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