Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4529a698ce7e1b11d4ba88619ff1e43292cc4c5e0bf8c1b34f9e587e9222426b

Tx prefix hash: 8b504ba6654f45aae7c9667e9c01c0bf965c19d4ba486a7685ebc99c5873b8fb
Tx public key: be322eaa73c7b329213a26c7ca7dde90806c00fcec6f8168539ea39631050b71
Timestamp: 1750867665 Timestamp [UCT]: 2025-06-25 16:07:45 Age [y:d:h:m:s]: 00:148:19:55:40
Block: 1312617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104317 RingCT/type: yes/0
Extra: 01be322eaa73c7b329213a26c7ca7dde90806c00fcec6f8168539ea39631050b71021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07ee0c290edae10a4b1027df19f479f0d63bfd8b4f070a3581ff987656b9942b 0.600000000000 1800250 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": 1312627, "vin": [ { "gen": { "height": 1312617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07ee0c290edae10a4b1027df19f479f0d63bfd8b4f070a3581ff987656b9942b" } } ], "extra": [ 1, 190, 50, 46, 170, 115, 199, 179, 41, 33, 58, 38, 199, 202, 125, 222, 144, 128, 108, 0, 252, 236, 111, 129, 104, 83, 158, 163, 150, 49, 5, 11, 113, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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