Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef9f229fecc420ae5d5addc4fd180378ce58a3da70bb2190240da037dff68dcb

Tx prefix hash: 7b8ae5fa5de41322665ee080119987fbcb70d9162811f66733b90ebd9e2cf983
Tx public key: ddbfa4df289848de120a87a1df73f5c293e9d82a3438de0db8c2a63fc47f68df
Timestamp: 1754948446 Timestamp [UCT]: 2025-08-11 21:40:46 Age [y:d:h:m:s]: 00:106:15:59:41
Block: 1345048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75519 RingCT/type: yes/0
Extra: 01ddbfa4df289848de120a87a1df73f5c293e9d82a3438de0db8c2a63fc47f68df021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06ca8de92e7b367d841659fbb53ed66c0b17b875841dac0a11809be6c52843b0 0.600000000000 1832937 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": 1345058, "vin": [ { "gen": { "height": 1345048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06ca8de92e7b367d841659fbb53ed66c0b17b875841dac0a11809be6c52843b0" } } ], "extra": [ 1, 221, 191, 164, 223, 40, 152, 72, 222, 18, 10, 135, 161, 223, 115, 245, 194, 147, 233, 216, 42, 52, 56, 222, 13, 184, 194, 166, 63, 196, 127, 104, 223, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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