Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a04ff50208dc85abc36235eeb61e0cb42f9431293a5d057626afdb2645cb2c8

Tx prefix hash: 2387fb43b1b35e30b74557d1738894a0de403340a26f89a8476d5e675f2696be
Tx public key: 7f4fcdb2e552286d1fa0e42142b7d2facf648e87cba4a71a6f047a56137a969b
Timestamp: 1763916227 Timestamp [UCT]: 2025-11-23 16:43:47 Age [y:d:h:m:s]: 00:043:04:02:54
Block: 1418515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30924 RingCT/type: yes/0
Extra: 017f4fcdb2e552286d1fa0e42142b7d2facf648e87cba4a71a6f047a56137a969b021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4b2fe8c42498239a0aff94cf3db2f4af026d75564860bd9e093bc527acf39da 0.600000000000 1907046 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": 1418525, "vin": [ { "gen": { "height": 1418515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4b2fe8c42498239a0aff94cf3db2f4af026d75564860bd9e093bc527acf39da" } } ], "extra": [ 1, 127, 79, 205, 178, 229, 82, 40, 109, 31, 160, 228, 33, 66, 183, 210, 250, 207, 100, 142, 135, 203, 164, 167, 26, 111, 4, 122, 86, 19, 122, 150, 155, 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