For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: dde99bbb1b3e4a59e330134f808de3180f1a4cc438381c3553c04817feb90846
Tx prefix hash: fee15d0a521209008e846289fc3eed7e3197cbdff0ed8ee59f7e0e5206963d34
Tx public key: 6114c33e883383b1ea27c48231e4cffe90ecb187b907ffae7e6e763bfa4a824a
| Timestamp: 1780075065 | Timestamp [UTC]: 2026-05-29 17:17:45 | Age [y:d:h:m:s]: 00:010:10:21:05 |
| Block: 4692 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3250 | RingCT/type: yes/0 |
| Extra: 016114c33e883383b1ea27c48231e4cffe90ecb187b907ffae7e6e763bfa4a824a02090000000226697be300 | ||
1 output(s) for total of 34.870968270186 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9161e7659a1209942274c9a62b4f48737531bb6c344a2277d9104e16a2a7bae | 34.870968270186 | 5894 of 0 | <da> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 4752,
"vin": [ {
"gen": {
"height": 4692
}
}
],
"vout": [ {
"amount": 34870968270186,
"target": {
"tagged_key": {
"key": "b9161e7659a1209942274c9a62b4f48737531bb6c344a2277d9104e16a2a7bae",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 97, 20, 195, 62, 136, 51, 131, 177, 234, 39, 196, 130, 49, 228, 207, 254, 144, 236, 177, 135, 185, 7, 255, 174, 126, 110, 118, 59, 250, 74, 130, 74, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}