Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314670714b8a1fbf753fa5078892c6dd61a1333abad6fd55f72a0168ffd652d8

Tx prefix hash: a4e645ad8004e9fee22077d745a0e91806398ae6e60c2188c81f742c335bcf3f
Tx public key: fb81db59577cb2cd04774595bdee3d3a10a80cc184b58f3a5a9e29b3d180266c
Timestamp: 1764494255 Timestamp [UCT]: 2025-11-30 09:17:35 Age [y:d:h:m:s]: 00:000:07:33:04
Block: 1423311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219 RingCT/type: yes/0
Extra: 01fb81db59577cb2cd04774595bdee3d3a10a80cc184b58f3a5a9e29b3d180266c021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9496c446dfd6943008731c765021d18eec84c989bdd494c9b0b6c2af273acfc 0.600000000000 1911916 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": 1423321, "vin": [ { "gen": { "height": 1423311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9496c446dfd6943008731c765021d18eec84c989bdd494c9b0b6c2af273acfc" } } ], "extra": [ 1, 251, 129, 219, 89, 87, 124, 178, 205, 4, 119, 69, 149, 189, 238, 61, 58, 16, 168, 12, 193, 132, 181, 143, 58, 90, 158, 41, 179, 209, 128, 38, 108, 2, 17, 0, 0, 0, 4, 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