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: 947dc3534cdbc52031dcea2154b88ebf607e0fec2d5b42180bc434a5ea3b6b3b
Tx prefix hash: 87de8f1161b3a5174f191dd73ab24ceb5bb926872f289eaf427089cc2e9da13c
Tx public key: 98feb95661ae6ef90c320e4186df0a98083725791ad878931fc29d1d1ca309dd
| Timestamp: 1780000659 | Timestamp [UTC]: 2026-05-28 20:37:39 | Age [y:d:h:m:s]: 00:011:06:02:57 |
| Block: 4058 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3838 | RingCT/type: yes/0 |
| Extra: 0198feb95661ae6ef90c320e4186df0a98083725791ad878931fc29d1d1ca309dd02090000000f26697be300 | ||
1 output(s) for total of 34.913161850145 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d73c1c7c112e765c371e57cfa7b311e5c18d9cd84a7205bfd410cd0595696d2 | 34.913161850145 | 5028 of 0 | <ea> |
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": 4118,
"vin": [ {
"gen": {
"height": 4058
}
}
],
"vout": [ {
"amount": 34913161850145,
"target": {
"tagged_key": {
"key": "3d73c1c7c112e765c371e57cfa7b311e5c18d9cd84a7205bfd410cd0595696d2",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 152, 254, 185, 86, 97, 174, 110, 249, 12, 50, 14, 65, 134, 223, 10, 152, 8, 55, 37, 121, 26, 216, 120, 147, 31, 194, 157, 29, 28, 163, 9, 221, 2, 9, 0, 0, 0, 15, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}