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: 31e60d9fe02328fae4335d703819f9d1f2507c34dea348f460fa56de56e400f9
Tx prefix hash: 45a2a98876bec058fd46cd610e559d41b8343d163b796b15fc4077aa33d61075
Tx public key: 22554c1e4da0bab6f9a337e69015b6f6d979203dc08c107459dca66ff27ba47a
| Timestamp: 1779717403 | Timestamp [UTC]: 2026-05-25 13:56:43 | Age [y:d:h:m:s]: 00:014:12:15:19 |
| Block: 1679 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6207 | RingCT/type: yes/0 |
| Extra: 0122554c1e4da0bab6f9a337e69015b6f6d979203dc08c107459dca66ff27ba47a020900000001ba6d17be00 | ||
1 output(s) for total of 35.071943319784 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf199c19e7b634660216ccc61159033a6017f749520f614f657a06b0e5ca65c1 | 35.071943319784 | 1846 of 0 | <3a> |
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": 1739,
"vin": [ {
"gen": {
"height": 1679
}
}
],
"vout": [ {
"amount": 35071943319784,
"target": {
"tagged_key": {
"key": "bf199c19e7b634660216ccc61159033a6017f749520f614f657a06b0e5ca65c1",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 34, 85, 76, 30, 77, 160, 186, 182, 249, 163, 55, 230, 144, 21, 182, 246, 217, 121, 32, 61, 192, 140, 16, 116, 89, 220, 166, 111, 242, 123, 164, 122, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}