Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b781320c7226d2b9f1eaa0d127b91882d4bcaf7473fd3976c6ad85be76cd62

Tx prefix hash: f4aea789e2333ed344cb5e5a799ac90948fe2fcb28d7d0d3d6f0b11af367d52e
Tx public key: 77a92e7438a707d5d3126eeb636697395e454dfa6608e7b8bdb93a933c3bfa41
Timestamp: 1703126636 Timestamp [UCT]: 2023-12-21 02:43:56 Age [y:d:h:m:s]: 01:293:04:22:59
Block: 917683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468316 RingCT/type: yes/0
Extra: 0177a92e7438a707d5d3126eeb636697395e454dfa6608e7b8bdb93a933c3bfa41021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae99760ba94cd0f9eb8597f216f8db7b54e1c62adf5fd9304560663ddd50050d 0.600000000000 1375265 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": 917693, "vin": [ { "gen": { "height": 917683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae99760ba94cd0f9eb8597f216f8db7b54e1c62adf5fd9304560663ddd50050d" } } ], "extra": [ 1, 119, 169, 46, 116, 56, 167, 7, 213, 211, 18, 110, 235, 99, 102, 151, 57, 94, 69, 77, 250, 102, 8, 231, 184, 189, 185, 58, 147, 60, 59, 250, 65, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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