Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a5e1eb0af93b79f9041b78aba6318ff3db1483f0c4126273751437a85574611

Tx prefix hash: a9a287389fd53fdaa72fdffa8f9d621135fc47ef1d042991568d67973bffef4e
Tx public key: 9e7a9c06abb723b6e32039388c4c36a80b404902e80714828e995589a078808a
Timestamp: 1699482898 Timestamp [UCT]: 2023-11-08 22:34:58 Age [y:d:h:m:s]: 01:218:05:45:38
Block: 887463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417126 RingCT/type: yes/0
Extra: 019e7a9c06abb723b6e32039388c4c36a80b404902e80714828e995589a078808a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.703828226000 dcy

stealth address amount amount idx
00: bb06d2ec40084f04517e4b00208efe9f99b7559362d4e1eab9fd0fe5fe4f5aa0 0.703828226000 1343346 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": 887473, "vin": [ { "gen": { "height": 887463 } } ], "vout": [ { "amount": 703828226, "target": { "key": "bb06d2ec40084f04517e4b00208efe9f99b7559362d4e1eab9fd0fe5fe4f5aa0" } } ], "extra": [ 1, 158, 122, 156, 6, 171, 183, 35, 182, 227, 32, 57, 56, 140, 76, 54, 168, 11, 64, 73, 2, 232, 7, 20, 130, 142, 153, 85, 137, 160, 120, 128, 138, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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