Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09a0fa117200be2b16e5d23181b35c78e27b11056c6d778c59832ca7fc39c245

Tx prefix hash: dbc108e560436e37bf318a00a8b4bb1aa934f59c2bb96df0ef18af5e2609ebd7
Tx public key: f9bcfc244dd93c3e929a56359583c832a4f8291652b4c208a754e9bd85a4e8db
Timestamp: 1750042135 Timestamp [UCT]: 2025-06-16 02:48:55 Age [y:d:h:m:s]: 00:157:17:44:08
Block: 1305962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110509 RingCT/type: yes/0
Extra: 01f9bcfc244dd93c3e929a56359583c832a4f8291652b4c208a754e9bd85a4e8db021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e3398928a27bb036641d63e639fbae5aa6e02affd51bc548547a309c1711330 0.600000000000 1793565 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": 1305972, "vin": [ { "gen": { "height": 1305962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e3398928a27bb036641d63e639fbae5aa6e02affd51bc548547a309c1711330" } } ], "extra": [ 1, 249, 188, 252, 36, 77, 217, 60, 62, 146, 154, 86, 53, 149, 131, 200, 50, 164, 248, 41, 22, 82, 180, 194, 8, 167, 84, 233, 189, 133, 164, 232, 219, 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