Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1addf6ca827219b66be8122b5405292dfd938c311adf2881875d52f6e044983

Tx prefix hash: 018dc6f1e18854cd67407132134c844767c4e39563bed7eb7cbff3e07325454c
Tx public key: d092c070cafa2878218cb2953a2cb5a927f6ce72e68122004009df9c64bbac4d
Timestamp: 1763288918 Timestamp [UCT]: 2025-11-16 10:28:38 Age [y:d:h:m:s]: 00:005:07:20:16
Block: 1413318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3786 RingCT/type: yes/0
Extra: 01d092c070cafa2878218cb2953a2cb5a927f6ce72e68122004009df9c64bbac4d021100000004fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9da7e1c7dc5e91a7512d7c511a67986a01fad1e248c86cf7e61956f2892de7b8 0.600000000000 1901797 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": 1413328, "vin": [ { "gen": { "height": 1413318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9da7e1c7dc5e91a7512d7c511a67986a01fad1e248c86cf7e61956f2892de7b8" } } ], "extra": [ 1, 208, 146, 192, 112, 202, 250, 40, 120, 33, 140, 178, 149, 58, 44, 181, 169, 39, 246, 206, 114, 230, 129, 34, 0, 64, 9, 223, 156, 100, 187, 172, 77, 2, 17, 0, 0, 0, 4, 251, 143, 208, 137, 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