Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79bd53474eb738e1d7349d3a0636d5a302407966c85ada6aa9c5823d66ddc94f

Tx prefix hash: a242282e9a00b5c8b161916bfdec3c428049a7af16ee30e7f2dbe8bed9fa1154
Tx public key: 121aee389be61d6719d696e64260dddeeb06d5e432f8f7cfc5d31c4e500ae4a4
Timestamp: 1752963065 Timestamp [UCT]: 2025-07-19 22:11:05 Age [y:d:h:m:s]: 00:116:21:37:37
Block: 1329109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82329 RingCT/type: yes/0
Extra: 01121aee389be61d6719d696e64260dddeeb06d5e432f8f7cfc5d31c4e500ae4a4021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6c3e7fd53d5ee0647b57de0421ebc9af0a2d967d2f32803ca84e43fec64e566 0.600000000000 1816884 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": 1329119, "vin": [ { "gen": { "height": 1329109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6c3e7fd53d5ee0647b57de0421ebc9af0a2d967d2f32803ca84e43fec64e566" } } ], "extra": [ 1, 18, 26, 238, 56, 155, 230, 29, 103, 25, 214, 150, 230, 66, 96, 221, 222, 235, 6, 213, 228, 50, 248, 247, 207, 197, 211, 28, 78, 80, 10, 228, 164, 2, 17, 0, 0, 0, 1, 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