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: 3db6075a42d0938599756fd28e80460be7aab9208ada05d394d4fac4490a6ff7
Tx prefix hash: 4f3ae4a3aaa0582ef6ce06c4f1b61c33b2c59e2365a5aec3be78f99f6fd041f6
Tx public key: 7afcf3f321a43205d5c0d4b686b6893709e4a4e1902c0a8ed9e59a18a38ebc0c
| Timestamp: 1780686301 | Timestamp [UTC]: 2026-06-05 19:05:01 | Age [y:d:h:m:s]: 00:003:08:45:57 |
| Block: 5419 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2533 | RingCT/type: yes/0 |
| Extra: 017afcf3f321a43205d5c0d4b686b6893709e4a4e1902c0a8ed9e59a18a38ebc0c020900000001e49593ff00 | ||
1 output(s) for total of 34.822648168113 HMNY
| stealth address | amount | amount idx | tag |
| 00: f47b4d06e0167e23cdae53473de5223ab451743a938743b9b9fe696410f7bfed | 34.822648168113 | 6856 of 0 | <3f> |
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": 5479,
"vin": [ {
"gen": {
"height": 5419
}
}
],
"vout": [ {
"amount": 34822648168113,
"target": {
"tagged_key": {
"key": "f47b4d06e0167e23cdae53473de5223ab451743a938743b9b9fe696410f7bfed",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 122, 252, 243, 243, 33, 164, 50, 5, 213, 192, 212, 182, 134, 182, 137, 55, 9, 228, 164, 225, 144, 44, 10, 142, 217, 229, 154, 24, 163, 142, 188, 12, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}