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: be10452935fe68b5a5a4242ad4868e873139b3d053eeff8e1e7432a026393a8b
Tx prefix hash: 0a162ef5f7f475ed06b160049dcea453cf61edae5d0394c9337a46a1a5643036
Tx public key: 1da904ef3c517f64e0d2ad5ac3bc2806ae29477b465574691317bdb863b25d3d
| Timestamp: 1780692818 | Timestamp [UTC]: 2026-06-05 20:53:38 | Age [y:d:h:m:s]: 00:003:04:42:19 |
| Block: 5820 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2066 | RingCT/type: yes/0 |
| Extra: 011da904ef3c517f64e0d2ad5ac3bc2806ae29477b465574691317bdb863b25d3d020900000001e49593ff00 | ||
1 output(s) for total of 34.796024334517 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4bf4957648efad04a74fe745ac8f5ed7094abcab0d51c95b3bce16521a2559d7 | 34.796024334517 | 7277 of 0 | <73> |
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": 5880,
"vin": [ {
"gen": {
"height": 5820
}
}
],
"vout": [ {
"amount": 34796024334517,
"target": {
"tagged_key": {
"key": "4bf4957648efad04a74fe745ac8f5ed7094abcab0d51c95b3bce16521a2559d7",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 29, 169, 4, 239, 60, 81, 127, 100, 224, 210, 173, 90, 195, 188, 40, 6, 174, 41, 71, 123, 70, 85, 116, 105, 19, 23, 189, 184, 99, 178, 93, 61, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}