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: 1f507f856d81ed95756fd299c696bc2ba32520e71b4760780a7b61d2934e8e67
Tx prefix hash: 61a3bff0eeda0238841508fcb01a3d0f14bae85ea5c78d2a0361a150c3540d46
Tx public key: 7f9b263a4017f4a9000d1c6163f32b1e4e2baa288ef2ac6178ffbc7b15b49d0e
| Timestamp: 1780047769 | Timestamp [UTC]: 2026-05-29 09:42:49 | Age [y:d:h:m:s]: 00:010:15:53:08 |
| Block: 4364 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3522 | RingCT/type: yes/0 |
| Extra: 017f9b263a4017f4a9000d1c6163f32b1e4e2baa288ef2ac6178ffbc7b15b49d0e02090000001226697be300 | ||
1 output(s) for total of 34.892790755191 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e95c1001cda689fd4d6f8039a6479f625b1dd61ca9b6c05601395540c95b434 | 34.892790755191 | 5457 of 0 | <7b> |
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": 4424,
"vin": [ {
"gen": {
"height": 4364
}
}
],
"vout": [ {
"amount": 34892790755191,
"target": {
"tagged_key": {
"key": "4e95c1001cda689fd4d6f8039a6479f625b1dd61ca9b6c05601395540c95b434",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 127, 155, 38, 58, 64, 23, 244, 169, 0, 13, 28, 97, 99, 243, 43, 30, 78, 43, 170, 40, 142, 242, 172, 97, 120, 255, 188, 123, 21, 180, 157, 14, 2, 9, 0, 0, 0, 18, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}