Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161bd0cd36a97edb5a53ce7118418e8097cd4516de0ecc1e33bc2f9f59b2ac40

Tx prefix hash: e85c9c146084b1d7dba48a4308e615887a4374b84e55477133b8398d15411434
Tx public key: dd4fcaf36bff98224492c7f7c8cca5219d5868c4ef4d3753a1dd9daae95016ae
Timestamp: 1765919296 Timestamp [UCT]: 2025-12-16 21:08:16 Age [y:d:h:m:s]: 00:013:23:53:27
Block: 1435105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10028 RingCT/type: yes/0
Extra: 01dd4fcaf36bff98224492c7f7c8cca5219d5868c4ef4d3753a1dd9daae95016ae0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27903baa03e6ac317a8e5d830382a7f7135d9ebffd8553bee21a67df06c717c7 0.600000000000 1923902 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": 1435115, "vin": [ { "gen": { "height": 1435105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27903baa03e6ac317a8e5d830382a7f7135d9ebffd8553bee21a67df06c717c7" } } ], "extra": [ 1, 221, 79, 202, 243, 107, 255, 152, 34, 68, 146, 199, 247, 200, 204, 165, 33, 157, 88, 104, 196, 239, 77, 55, 83, 161, 221, 157, 170, 233, 80, 22, 174, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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