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: aef492a46ebdf566671c6d5aa63f98046c1806e5d39da048124541bf84ea8a1c
Tx prefix hash: fc5ca3e7938b3cb6fa6d34d50b0f29c6482bf3a38d5b2f68da0763fc08329915
Tx public key: 3d86cfd69d53bdf973b938b5c301329cd0cc629849d790ac5dde839c6f825f0b
| Timestamp: 1779603812 | Timestamp [UTC]: 2026-05-24 06:23:32 | Age [y:d:h:m:s]: 00:015:19:12:25 |
| Block: 731 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7155 | RingCT/type: yes/0 |
| Extra: 013d86cfd69d53bdf973b938b5c301329cd0cc629849d790ac5dde839c6f825f0b | ||
1 output(s) for total of 35.135416661346 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1bc26d31db3c2f7e1846eef6475de015a84c122bbd4765e170738b8fbe437669 | 35.135416661346 | 861 of 0 | <12> |
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": 791,
"vin": [ {
"gen": {
"height": 731
}
}
],
"vout": [ {
"amount": 35135416661346,
"target": {
"tagged_key": {
"key": "1bc26d31db3c2f7e1846eef6475de015a84c122bbd4765e170738b8fbe437669",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 61, 134, 207, 214, 157, 83, 189, 249, 115, 185, 56, 181, 195, 1, 50, 156, 208, 204, 98, 152, 73, 215, 144, 172, 93, 222, 131, 156, 111, 130, 95, 11
],
"rct_signatures": {
"type": 0
}
}