Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d24fe16dbf57805ec865420f31879bc3db9b5ca6f244bb6074b06b84690bab

Tx prefix hash: c556d2e4631ae02c3e6d5e5d57f34747b89f7de213abf5e82195dc1f456292ec
Tx public key: 6af60cad71a3da3c8df34067e380019dab0a0a3131b2e7fa277d96d14bce1bd0
Timestamp: 1702811782 Timestamp [UCT]: 2023-12-17 11:16:22 Age [y:d:h:m:s]: 01:146:16:27:13
Block: 915062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365979 RingCT/type: yes/0
Extra: 016af60cad71a3da3c8df34067e380019dab0a0a3131b2e7fa277d96d14bce1bd002110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf64b51c4ad6194ab6ecbcd073be47a1fbf05b68d17b43605059171aa49acb79 0.600000000000 1372442 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": 915072, "vin": [ { "gen": { "height": 915062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf64b51c4ad6194ab6ecbcd073be47a1fbf05b68d17b43605059171aa49acb79" } } ], "extra": [ 1, 106, 246, 12, 173, 113, 163, 218, 60, 141, 243, 64, 103, 227, 128, 1, 157, 171, 10, 10, 49, 49, 178, 231, 250, 39, 125, 150, 209, 75, 206, 27, 208, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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