Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 001b30f0b98189c472eca7c834cbecda793da16ec8752ef756d9e8443e68b69e

Tx prefix hash: 2dc52c0a0f8f6543e9b2834ad89a80612e603e0e1b0f8600b63225d5076bd9be
Tx public key: a117f335db8f2b2783d9f9c7d228428fe8560b6d4dbcb1118405997f62cb025d
Timestamp: 1756098438 Timestamp [UCT]: 2025-08-25 05:07:18 Age [y:d:h:m:s]: 00:135:06:58:26
Block: 1353901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96705 RingCT/type: yes/0
Extra: 01a117f335db8f2b2783d9f9c7d228428fe8560b6d4dbcb1118405997f62cb025d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 199589dd43318ef871afc1226ac6cfddc595aa817bf32bc3ae2f6edfbca11a0f 0.600000000000 1841880 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": 1353911, "vin": [ { "gen": { "height": 1353901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "199589dd43318ef871afc1226ac6cfddc595aa817bf32bc3ae2f6edfbca11a0f" } } ], "extra": [ 1, 161, 23, 243, 53, 219, 143, 43, 39, 131, 217, 249, 199, 210, 40, 66, 143, 232, 86, 11, 109, 77, 188, 177, 17, 132, 5, 153, 127, 98, 203, 2, 93, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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