Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495f694bc90bd4d84e3f197fc7dc8bbe2d9d91de60113f29c0d38404e558be35

Tx prefix hash: f17cc171498502ec727a6f66fd53d75669f7a9dcfb7b66e9f43efd7aa0009d3d
Tx public key: 4b20e14a1dd67866b6bab3afb8076a30b178a73a183481925b335a059fcc71ce
Timestamp: 1744385628 Timestamp [UCT]: 2025-04-11 15:33:48 Age [y:d:h:m:s]: 00:290:21:01:25
Block: 1259230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205519 RingCT/type: yes/0
Extra: 014b20e14a1dd67866b6bab3afb8076a30b178a73a183481925b335a059fcc71ce0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dcbd5949c99d442a521da174d5f9c5b773cc6c747cc250065e59efa400cefb3 0.600000000000 1746369 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": 1259240, "vin": [ { "gen": { "height": 1259230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dcbd5949c99d442a521da174d5f9c5b773cc6c747cc250065e59efa400cefb3" } } ], "extra": [ 1, 75, 32, 225, 74, 29, 214, 120, 102, 182, 186, 179, 175, 184, 7, 106, 48, 177, 120, 167, 58, 24, 52, 129, 146, 91, 51, 90, 5, 159, 204, 113, 206, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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