Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b59358362a4e58e41f8a118241aaf31c785067b0e992dab1968b6d68c3bb3038

Tx prefix hash: 97707134fab7c4b91be35791a2fa495407c5c534356ae6142bec24cb9b49ec28
Tx public key: 475d977b38fd0ad7d9709d6426ce14d1a9dd559179b00d33be4a379b197576ba
Timestamp: 1581516066 Timestamp [UCT]: 2020-02-12 14:01:06 Age [y:d:h:m:s]: 04:325:03:02:30
Block: 63534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124477 RingCT/type: yes/0
Extra: 01475d977b38fd0ad7d9709d6426ce14d1a9dd559179b00d33be4a379b197576ba02110000000156c366d3000000000000000000

1 output(s) for total of 378.016290430000 dcy

stealth address amount amount idx
00: b13ed29467df6b5b404eeb2f014fc6a63e1f2e61a1ba7620cb3b58d251d79da5 378.016290430000 117108 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": 63544, "vin": [ { "gen": { "height": 63534 } } ], "vout": [ { "amount": 378016290430, "target": { "key": "b13ed29467df6b5b404eeb2f014fc6a63e1f2e61a1ba7620cb3b58d251d79da5" } } ], "extra": [ 1, 71, 93, 151, 123, 56, 253, 10, 215, 217, 112, 157, 100, 38, 206, 20, 209, 169, 221, 85, 145, 121, 176, 13, 51, 190, 74, 55, 155, 25, 117, 118, 186, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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