Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b4678f67e438cd11fd6b887da8b88c9c12d5d01b0690d14d249322c395cb3f5

Tx prefix hash: 41566c45dd070f98fae3d9faabbc63278fa0138e0f4c4a92b67ec7f1d3babe98
Tx public key: 6fe078b8f2cd58fc893371772ead1888294fae04926c9908a2b997afc7dde73d
Timestamp: 1712869249 Timestamp [UCT]: 2024-04-11 21:00:49 Age [y:d:h:m:s]: 00:357:22:34:47
Block: 998417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255914 RingCT/type: yes/0
Extra: 016fe078b8f2cd58fc893371772ead1888294fae04926c9908a2b997afc7dde73d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62ed8cfac8332d729b354014b2681f682ce8e9b470a42d9b0f6b12dcaa7b5a43 0.600000000000 1458867 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": 998427, "vin": [ { "gen": { "height": 998417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62ed8cfac8332d729b354014b2681f682ce8e9b470a42d9b0f6b12dcaa7b5a43" } } ], "extra": [ 1, 111, 224, 120, 184, 242, 205, 88, 252, 137, 51, 113, 119, 46, 173, 24, 136, 41, 79, 174, 4, 146, 108, 153, 8, 162, 185, 151, 175, 199, 221, 231, 61, 2, 17, 0, 0, 0, 5, 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