Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f9a029d3b4796fa476f99e63a2562c072f03157277b443d12438a7ac8bfd24

Tx prefix hash: fc1bd9b40151efda6d5e655e28c539f5b6777fdc865253f75ab8079d9bed0a9b
Tx public key: d453e538fe238e0718b196e5d3475f5b543ca72faf4cd911cd758829530a7720
Timestamp: 1687212726 Timestamp [UCT]: 2023-06-19 22:12:06 Age [y:d:h:m:s]: 01:213:08:44:24
Block: 785986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413886 RingCT/type: yes/0
Extra: 01d453e538fe238e0718b196e5d3475f5b543ca72faf4cd911cd758829530a772002110000000283600029000000000000000000

1 output(s) for total of 1.526519140000 dcy

stealth address amount amount idx
00: 2d033d76877b9f80f48b8ce78a4f5ff5c7aa922ad2d4e8636ba8522372f1ac51 1.526519140000 1235961 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": 785996, "vin": [ { "gen": { "height": 785986 } } ], "vout": [ { "amount": 1526519140, "target": { "key": "2d033d76877b9f80f48b8ce78a4f5ff5c7aa922ad2d4e8636ba8522372f1ac51" } } ], "extra": [ 1, 212, 83, 229, 56, 254, 35, 142, 7, 24, 177, 150, 229, 211, 71, 95, 91, 84, 60, 167, 47, 175, 76, 217, 17, 205, 117, 136, 41, 83, 10, 119, 32, 2, 17, 0, 0, 0, 2, 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