Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc68622eb76e31902da2aec649bff1cd757b262f36f4479cd88a3512004b75c7

Tx prefix hash: d827af69d575b9f0e8a812ad3a1dd093f5a513cdd8d60a77cae52900cd87f63e
Tx public key: 51e6e16f73154f74326fa29eccd83c70e09a2d3d70f3959b62777dde2d4c0672
Timestamp: 1676605230 Timestamp [UCT]: 2023-02-17 03:40:30 Age [y:d:h:m:s]: 01:271:21:58:01
Block: 698682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455235 RingCT/type: yes/0
Extra: 0151e6e16f73154f74326fa29eccd83c70e09a2d3d70f3959b62777dde2d4c067202110000000174b6d784000000000000000000

1 output(s) for total of 2.971504638000 dcy

stealth address amount amount idx
00: 7d3dc72ae0b2dd612fa0e4b1c3f12d9ff87873bac672b7daf02569449384eeec 2.971504638000 1142021 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": 698692, "vin": [ { "gen": { "height": 698682 } } ], "vout": [ { "amount": 2971504638, "target": { "key": "7d3dc72ae0b2dd612fa0e4b1c3f12d9ff87873bac672b7daf02569449384eeec" } } ], "extra": [ 1, 81, 230, 225, 111, 115, 21, 79, 116, 50, 111, 162, 158, 204, 216, 60, 112, 224, 154, 45, 61, 112, 243, 149, 155, 98, 119, 125, 222, 45, 76, 6, 114, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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