Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0047b30c37410ea9028b2c073948dfaed3cb332c838187b9b7c486e3b1a7ef8

Tx prefix hash: d1b5bd2ca29417d78808e0d112fa4ef6b97cbcfbfa8dad70767270801d399561
Tx public key: b58b5753b5e07883abc7758078c4235df4d7c36ff9e185a9ac2f66dc967a5951
Timestamp: 1670182174 Timestamp [UCT]: 2022-12-04 19:29:34 Age [y:d:h:m:s]: 02:112:10:54:25
Block: 645446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602045 RingCT/type: yes/0
Extra: 01b58b5753b5e07883abc7758078c4235df4d7c36ff9e185a9ac2f66dc967a595102110000000383600029000000000000000000

1 output(s) for total of 4.460355331000 dcy

stealth address amount amount idx
00: 7f3216f9b46cebef44d79f19408af9ae17ebcdf2ab0a4d25481699b9efa47cf1 4.460355331000 1085613 of 0

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": 645456, "vin": [ { "gen": { "height": 645446 } } ], "vout": [ { "amount": 4460355331, "target": { "key": "7f3216f9b46cebef44d79f19408af9ae17ebcdf2ab0a4d25481699b9efa47cf1" } } ], "extra": [ 1, 181, 139, 87, 83, 181, 224, 120, 131, 171, 199, 117, 128, 120, 196, 35, 93, 244, 215, 195, 111, 249, 225, 133, 169, 172, 47, 102, 220, 150, 122, 89, 81, 2, 17, 0, 0, 0, 3, 131, 96, 0, 41, 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