Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e2e006b8ca5b525019c92345b4f147d0b12168d25f1537848a2fc47984dc42a

Tx prefix hash: be68ac2e417a35ce24c86c0442436b94d927811122317724ce7d960143062303
Tx public key: 651e09e4b44a0e10f8be59ee21b52fa5558740b197e3bdae0bd34b8d7ea23481
Timestamp: 1680951302 Timestamp [UCT]: 2023-04-08 10:55:02 Age [y:d:h:m:s]: 02:213:07:48:46
Block: 734185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 672207 RingCT/type: yes/0
Extra: 01651e09e4b44a0e10f8be59ee21b52fa5558740b197e3bdae0bd34b8d7ea23481021100000005b3164c24000000000000000000

1 output(s) for total of 2.266420797000 dcy

stealth address amount amount idx
00: e170c7030b7c73ceaa82019b0dc68d6ffdff184b3e772d11a750d5111f87925e 2.266420797000 1180352 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": 734195, "vin": [ { "gen": { "height": 734185 } } ], "vout": [ { "amount": 2266420797, "target": { "key": "e170c7030b7c73ceaa82019b0dc68d6ffdff184b3e772d11a750d5111f87925e" } } ], "extra": [ 1, 101, 30, 9, 228, 180, 74, 14, 16, 248, 190, 89, 238, 33, 181, 47, 165, 85, 135, 64, 177, 151, 227, 189, 174, 11, 211, 75, 141, 126, 162, 52, 129, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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