Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c184dbe0a53821bfaa001d443529569ba86669333822aa07329491905320a373

Tx prefix hash: a1854016073d9cce0dd605bfd3957ccdf94e7ce6a7c75ee2f2bf703b062600cc
Tx public key: 22c9fe9297117244f1c5ed0943de2c2fd15457cae6a30a8d3e1aa7f22dd3e202
Timestamp: 1707191704 Timestamp [UCT]: 2024-02-06 03:55:04 Age [y:d:h:m:s]: 01:135:08:50:50
Block: 951354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357695 RingCT/type: yes/0
Extra: 0122c9fe9297117244f1c5ed0943de2c2fd15457cae6a30a8d3e1aa7f22dd3e20202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e73bc55f904eaeef106be7fd66153d4f64d622605e7a4ab2105352e350d8b0e 0.600000000000 1410108 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": 951364, "vin": [ { "gen": { "height": 951354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e73bc55f904eaeef106be7fd66153d4f64d622605e7a4ab2105352e350d8b0e" } } ], "extra": [ 1, 34, 201, 254, 146, 151, 17, 114, 68, 241, 197, 237, 9, 67, 222, 44, 47, 209, 84, 87, 202, 230, 163, 10, 141, 62, 26, 167, 242, 45, 211, 226, 2, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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