Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52ab919f6e2cd7f7c0eda99d27cc23bd3bb307a286bca343208869e81f8a7de

Tx prefix hash: 5d8ba358623ca5ae410c9a7a225b9e29a81791cb1b9fd2ff74c8590525523760
Tx public key: be8ab658787bce22fc43e3fe92400cbeab6a040e3084a5d9d95a653e921cad74
Timestamp: 1721318652 Timestamp [UCT]: 2024-07-18 16:04:12 Age [y:d:h:m:s]: 01:082:16:56:25
Block: 1068508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317549 RingCT/type: yes/0
Extra: 01be8ab658787bce22fc43e3fe92400cbeab6a040e3084a5d9d95a653e921cad7402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 546b87849b3393ac6a07a0adc98bb403efc9c6e7f60f19cf06f458f20b89f9cf 0.600000000000 1539587 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": 1068518, "vin": [ { "gen": { "height": 1068508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "546b87849b3393ac6a07a0adc98bb403efc9c6e7f60f19cf06f458f20b89f9cf" } } ], "extra": [ 1, 190, 138, 182, 88, 120, 123, 206, 34, 252, 67, 227, 254, 146, 64, 12, 190, 171, 106, 4, 14, 48, 132, 165, 217, 217, 90, 101, 62, 146, 28, 173, 116, 2, 17, 0, 0, 0, 5, 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