Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56a7e98efacc9122090b27af25bd193802cd7d3b8916961cb1f90e81dd057eca

Tx prefix hash: 209f3fbaabfc8047e552c37e3dc1a308f4610b29bade12bb8e94fea7c2342b3f
Tx public key: 1c71bdb3d74c1cd498a73a13454cfdf434d51ffe71bf20e05a4a9cae5a6dc716
Timestamp: 1716475558 Timestamp [UCT]: 2024-05-23 14:45:58 Age [y:d:h:m:s]: 00:312:07:39:26
Block: 1028345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223212 RingCT/type: yes/0
Extra: 011c71bdb3d74c1cd498a73a13454cfdf434d51ffe71bf20e05a4a9cae5a6dc716021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e34b25be6470c34fcc5461f0d95ef3ca40b6724794c57ecb3340c4efc44f5845 0.600000000000 1496334 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": 1028355, "vin": [ { "gen": { "height": 1028345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e34b25be6470c34fcc5461f0d95ef3ca40b6724794c57ecb3340c4efc44f5845" } } ], "extra": [ 1, 28, 113, 189, 179, 215, 76, 28, 212, 152, 167, 58, 19, 69, 76, 253, 244, 52, 213, 31, 254, 113, 191, 32, 224, 90, 74, 156, 174, 90, 109, 199, 22, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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