Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4b6a7771393ba922554548669f14e471cc4537181740c66845d1cfa2caa6c19

Tx prefix hash: 0ee313c5869c927cdbfa788d93b7698b1568b0330bb5939efe9d7e98a374d766
Tx public key: d3e66543c0e0b01aa42293cc80377f30c01369e69eb4d0e3226cbbc9eefccdac
Timestamp: 1763494790 Timestamp [UCT]: 2025-11-18 19:39:50 Age [y:d:h:m:s]: 00:051:10:15:57
Block: 1415017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36832 RingCT/type: yes/0
Extra: 01d3e66543c0e0b01aa42293cc80377f30c01369e69eb4d0e3226cbbc9eefccdac021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf0b25eaecd4b8e43abac393a4464b465414ad9796b080aa869e90b8f3351098 0.600000000000 1903510 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": 1415027, "vin": [ { "gen": { "height": 1415017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf0b25eaecd4b8e43abac393a4464b465414ad9796b080aa869e90b8f3351098" } } ], "extra": [ 1, 211, 230, 101, 67, 192, 224, 176, 26, 164, 34, 147, 204, 128, 55, 127, 48, 192, 19, 105, 230, 158, 180, 208, 227, 34, 108, 187, 201, 238, 252, 205, 172, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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