Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60b2192e0703784b16b2ec4af8c4be99016f32a0d230d2d29dee932488b7465

Tx prefix hash: ff17bc788f78fbdf702e90ee128b27df7ce4b17b15bf118f24b03aa90de360a2
Tx public key: 7686e2b9a602d850e406cfb24ae3e0c29b02d597331c416a01cdaf5b625ba227
Timestamp: 1720199359 Timestamp [UCT]: 2024-07-05 17:09:19 Age [y:d:h:m:s]: 00:273:11:49:17
Block: 1059201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195406 RingCT/type: yes/0
Extra: 017686e2b9a602d850e406cfb24ae3e0c29b02d597331c416a01cdaf5b625ba2270211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ddf2da4c2bfbab86efb80e139d507808f5c7a22d4ae0fa12bcd1058ffb9824e 0.600000000000 1529666 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": 1059211, "vin": [ { "gen": { "height": 1059201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ddf2da4c2bfbab86efb80e139d507808f5c7a22d4ae0fa12bcd1058ffb9824e" } } ], "extra": [ 1, 118, 134, 226, 185, 166, 2, 216, 80, 228, 6, 207, 178, 74, 227, 224, 194, 155, 2, 213, 151, 51, 28, 65, 106, 1, 205, 175, 91, 98, 91, 162, 39, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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