Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38a672da0167e54e3b678c8e6a8c15de6623e234e9095278603fe532893f1af5

Tx prefix hash: 695c84bb6d9434d80eacdd8597b0e0387f0c5c3f00104a29bec7338e6f4c75ff
Tx public key: f62b7a634f9c8d0c75bc54277dac985ab74f12fc12e2807f1a6bca32fe5522ea
Timestamp: 1736192149 Timestamp [UCT]: 2025-01-06 19:35:49 Age [y:d:h:m:s]: 00:108:20:04:44
Block: 1191661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77583 RingCT/type: yes/0
Extra: 01f62b7a634f9c8d0c75bc54277dac985ab74f12fc12e2807f1a6bca32fe5522ea0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0bf352004670ee3cbd54852ac26d83be0e7d417de286227e7c720dae4a047f0 0.600000000000 1678202 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": 1191671, "vin": [ { "gen": { "height": 1191661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0bf352004670ee3cbd54852ac26d83be0e7d417de286227e7c720dae4a047f0" } } ], "extra": [ 1, 246, 43, 122, 99, 79, 156, 141, 12, 117, 188, 84, 39, 125, 172, 152, 90, 183, 79, 18, 252, 18, 226, 128, 127, 26, 107, 202, 50, 254, 85, 34, 234, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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