Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 096322fa05e93bfc8cd0f32ef5386837cfe61975d69a4e384623471ab326bd54

Tx prefix hash: dc8f7b6e8f93fb1c50c10ee82337c1f5fb7daf742f194d4e647ac2f2dbb44109
Tx public key: c21a88e9dc2257a6987e2b183618b5c131d4c31e36f5a7748582af4cd46bebcc
Timestamp: 1765959027 Timestamp [UCT]: 2025-12-17 08:10:27 Age [y:d:h:m:s]: 00:006:13:54:08
Block: 1435433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4711 RingCT/type: yes/0
Extra: 01c21a88e9dc2257a6987e2b183618b5c131d4c31e36f5a7748582af4cd46bebcc021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f2f919f757be31dffbb48654b5ccdcb8419d741eb6938cf0ce999f87693a820 0.600000000000 1924230 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": 1435443, "vin": [ { "gen": { "height": 1435433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f2f919f757be31dffbb48654b5ccdcb8419d741eb6938cf0ce999f87693a820" } } ], "extra": [ 1, 194, 26, 136, 233, 220, 34, 87, 166, 152, 126, 43, 24, 54, 24, 181, 193, 49, 212, 195, 30, 54, 245, 167, 116, 133, 130, 175, 76, 212, 107, 235, 204, 2, 17, 0, 0, 0, 7, 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