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: 87d156e2d22372ec704e086a2536e3f9c4c1ef01cfc113384f3763b2c17d9d11
Tx prefix hash: 2c226383bc14b0dce9dec6ff2c3579dc4e005f5b376a1313bdc1c7cee6ba62aa
Tx public key: a2aaf00e5c1faff3c25e179036f98cb97fe5ed37dbe296a4c4bb8c605bd08ba5
| Timestamp: 1779990190 | Timestamp [UTC]: 2026-05-28 17:43:10 | Age [y:d:h:m:s]: 00:011:07:52:47 |
| Block: 3990 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3896 | RingCT/type: yes/0 |
| Extra: 01a2aaf00e5c1faff3c25e179036f98cb97fe5ed37dbe296a4c4bb8c605bd08ba502090000000226697be300 | ||
1 output(s) for total of 34.917690374995 HMNY
| stealth address | amount | amount idx | tag |
| 00: 89417dc2bd731f280ff68ab6522740a7219ec6ec42a5e9563ee8095fc910b3fb | 34.917690374995 | 4926 of 0 | <d8> |
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": 4050,
"vin": [ {
"gen": {
"height": 3990
}
}
],
"vout": [ {
"amount": 34917690374995,
"target": {
"tagged_key": {
"key": "89417dc2bd731f280ff68ab6522740a7219ec6ec42a5e9563ee8095fc910b3fb",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 162, 170, 240, 14, 92, 31, 175, 243, 194, 94, 23, 144, 54, 249, 140, 185, 127, 229, 237, 55, 219, 226, 150, 164, 196, 187, 140, 96, 91, 208, 139, 165, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}