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: 31b804172059a8145854f675570094120f5db176c22870bcd69174e3e02b090d
Tx prefix hash: 0df8b5bb8f4da3ed7fa2f9b7cc93f11df788c12ae36b86773741f6fe98bda41e
Tx public key: 3cf829ae2119564bb93fc09ca209d43d90dc70f1b9de4b3d3bba1071f39a42af
| Timestamp: 1779912824 | Timestamp [UTC]: 2026-05-27 20:13:44 | Age [y:d:h:m:s]: 00:012:03:05:09 |
| Block: 3264 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4622 | RingCT/type: yes/0 |
| Extra: 013cf829ae2119564bb93fc09ca209d43d90dc70f1b9de4b3d3bba1071f39a42af02090000000426697be300 | ||
1 output(s) for total of 34.966075665545 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d4c908eb0ca838e9e64139bea867c668a2584ede7ec42b58a8930893c759b2c | 34.966075665545 | 3918 of 0 | <4b> |
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": 3324,
"vin": [ {
"gen": {
"height": 3264
}
}
],
"vout": [ {
"amount": 34966075665545,
"target": {
"tagged_key": {
"key": "9d4c908eb0ca838e9e64139bea867c668a2584ede7ec42b58a8930893c759b2c",
"view_tag": "4b"
}
}
}
],
"extra": [ 1, 60, 248, 41, 174, 33, 25, 86, 75, 185, 63, 192, 156, 162, 9, 212, 61, 144, 220, 112, 241, 185, 222, 75, 61, 59, 186, 16, 113, 243, 154, 66, 175, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}