Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0494885971fa1c098b41dcbbadaae7c78ed9d6d8110f8f7ba6996b42451c679c

Tx prefix hash: 02b8887947e67f4d1a61dab645a61e61a5f5dc7a53fe6a17a614a15ac71c5ff8
Tx public key: 3dac7fdc25c3a77ca559bbc24b3b8796059f9ddf33bdf1c4f73d92155381e220
Timestamp: 1758663895 Timestamp [UCT]: 2025-09-23 21:44:55 Age [y:d:h:m:s]: 00:047:02:41:40
Block: 1374979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33741 RingCT/type: yes/0
Extra: 013dac7fdc25c3a77ca559bbc24b3b8796059f9ddf33bdf1c4f73d92155381e220021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04ef009df246e19d70c999c04622e97e910a7e619cf91337b3a8bd404ba5644 0.600000000000 1863064 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": 1374989, "vin": [ { "gen": { "height": 1374979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04ef009df246e19d70c999c04622e97e910a7e619cf91337b3a8bd404ba5644" } } ], "extra": [ 1, 61, 172, 127, 220, 37, 195, 167, 124, 165, 89, 187, 194, 75, 59, 135, 150, 5, 159, 157, 223, 51, 189, 241, 196, 247, 61, 146, 21, 83, 129, 226, 32, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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