Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ba16e2565102a32b572e1dc4f904e593a2876738960c7a112c6e21dc1a7710c

Tx prefix hash: 2c6c168eedc25fbd923e3982106e669188e860a379c648f33d8231dd849652e1
Tx public key: 11e06899fbd9ad7d82262c43d9cfc81d4440e0103c1d4b9cdf277fffd1fdacaa
Timestamp: 1710891838 Timestamp [UCT]: 2024-03-19 23:43:58 Age [y:d:h:m:s]: 01:231:23:44:52
Block: 982063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424468 RingCT/type: yes/0
Extra: 0111e06899fbd9ad7d82262c43d9cfc81d4440e0103c1d4b9cdf277fffd1fdacaa02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2834ec27ca633bfb047682f2e10266f1a24b11a06d741952708819e108d3cae 0.600000000000 1442166 of 15

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": 982073, "vin": [ { "gen": { "height": 982063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2834ec27ca633bfb047682f2e10266f1a24b11a06d741952708819e108d3cae" } } ], "extra": [ 1, 17, 224, 104, 153, 251, 217, 173, 125, 130, 38, 44, 67, 217, 207, 200, 29, 68, 64, 224, 16, 60, 29, 75, 156, 223, 39, 127, 255, 209, 253, 172, 170, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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