Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a83d8dcfbe5e9cae9cab1e53a4144dcece52cc10e9c7664d2505e87954cb7312

Tx prefix hash: 18392b4b3beef7678ff46e220370be1149cb5eccf64096e57f9ea9dd5e147839
Tx public key: 19c8fcb770bfa8ff5d2bff713970f3b7378bcd8467d0bf9865367d9b9a9d4050
Timestamp: 1752732258 Timestamp [UCT]: 2025-07-17 06:04:18 Age [y:d:h:m:s]: 00:038:13:45:13
Block: 1327216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26417 RingCT/type: yes/0
Extra: 0119c8fcb770bfa8ff5d2bff713970f3b7378bcd8467d0bf9865367d9b9a9d405002110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db4f7f3d125c66726dc599308e66bc5e4970686faf036d325c55759ad7702d3 0.600000000000 1814969 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": 1327226, "vin": [ { "gen": { "height": 1327216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db4f7f3d125c66726dc599308e66bc5e4970686faf036d325c55759ad7702d3" } } ], "extra": [ 1, 25, 200, 252, 183, 112, 191, 168, 255, 93, 43, 255, 113, 57, 112, 243, 183, 55, 139, 205, 132, 103, 208, 191, 152, 101, 54, 125, 155, 154, 157, 64, 80, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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