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: 40fc16ba89088e169158530cb2fd55c2283c7ffb54d65c41d3a1d82227fa2fe7
Tx prefix hash: ebd64a8ca524851bb4d85071bf9ab1b36341be19b56643543252afbdd58a1d75
Tx public key: 87cca9f226d9ee9cc8fd28701667325eccb2ba869cbfc3f62883f6b51a7cf8dc
| Timestamp: 1780976047 | Timestamp [UTC]: 2026-06-09 03:34:07 | Age [y:d:h:m:s]: 00:000:07:52:41 |
| Block: 7933 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 580 | RingCT/type: yes/0 |
| Extra: 0187cca9f226d9ee9cc8fd28701667325eccb2ba869cbfc3f62883f6b51a7cf8dc020900000001e49593ff00 | ||
1 output(s) for total of 34.656070513592 HMNY
| stealth address | amount | amount idx | tag |
| 00: b8350ce5915e59ddf622c259a5c3d880022a8ecdeabb9fada0318405ef32179a | 34.656070513592 | 9839 of 0 | <c5> |
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": 7993,
"vin": [ {
"gen": {
"height": 7933
}
}
],
"vout": [ {
"amount": 34656070513592,
"target": {
"tagged_key": {
"key": "b8350ce5915e59ddf622c259a5c3d880022a8ecdeabb9fada0318405ef32179a",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 135, 204, 169, 242, 38, 217, 238, 156, 200, 253, 40, 112, 22, 103, 50, 94, 204, 178, 186, 134, 156, 191, 195, 246, 40, 131, 246, 181, 26, 124, 248, 220, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}