Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa0b18d2e6ec9c8932e6f9ce4f66302723895e05e4ecf944f54d7287ccba1f39

Tx prefix hash: 77ef4ff6daa2fa724555a03f94e4365db764d8b9ac6587e7c6c671efd0eac740
Tx public key: 9f55a6698f84d95d8976cdd4a36822017d869384cbdc917fa8f7764b3f50fb0e
Timestamp: 1752726183 Timestamp [UCT]: 2025-07-17 04:23:03 Age [y:d:h:m:s]: 00:119:15:03:41
Block: 1327171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84258 RingCT/type: yes/0
Extra: 019f55a6698f84d95d8976cdd4a36822017d869384cbdc917fa8f7764b3f50fb0e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3401a78b5a4085a65b6568559f49493d60be486eaaa8c8d1b11c7ce9bf1c209 0.600000000000 1814924 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": 1327181, "vin": [ { "gen": { "height": 1327171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3401a78b5a4085a65b6568559f49493d60be486eaaa8c8d1b11c7ce9bf1c209" } } ], "extra": [ 1, 159, 85, 166, 105, 143, 132, 217, 93, 137, 118, 205, 212, 163, 104, 34, 1, 125, 134, 147, 132, 203, 220, 145, 127, 168, 247, 118, 75, 63, 80, 251, 14, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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