Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe57a8c82562487d0df8ce704d7100871236e4a2c3f03dcb6bfe3562217b9ef1

Tx prefix hash: 6de59c1c896a8805126d8d67adc2ba6808236935cf3072ec6e8b95ca3c03fc33
Tx public key: d85bf956babdb387a7d3685bf90e5bc396de058eebc1a82afb851c4185fbb7e4
Timestamp: 1749924006 Timestamp [UCT]: 2025-06-14 18:00:06 Age [y:d:h:m:s]: 00:159:07:33:47
Block: 1305003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111613 RingCT/type: yes/0
Extra: 01d85bf956babdb387a7d3685bf90e5bc396de058eebc1a82afb851c4185fbb7e4021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19c8fdb75c91b626f09d2c1e3c44afd8364616be9e46941dfadad10016c553ca 0.600000000000 1792600 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": 1305013, "vin": [ { "gen": { "height": 1305003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19c8fdb75c91b626f09d2c1e3c44afd8364616be9e46941dfadad10016c553ca" } } ], "extra": [ 1, 216, 91, 249, 86, 186, 189, 179, 135, 167, 211, 104, 91, 249, 14, 91, 195, 150, 222, 5, 142, 235, 193, 168, 42, 251, 133, 28, 65, 133, 251, 183, 228, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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