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: 4765fa25955938eb32c12a9796bc901bf7865ecf3969d1bbcde9f00604691f17
Tx prefix hash: 40aa942fd755fcb9a49807f9fb318c16ad196d05db86c53b73e9337d694b978d
Tx public key: 862a3804a8f27ce792078f34a76e07f3abb9da77377c4c62c17f49e491e52092
| Timestamp: 1780695999 | Timestamp [UTC]: 2026-06-05 21:46:39 | Age [y:d:h:m:s]: 00:003:03:49:18 |
| Block: 5981 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1905 | RingCT/type: yes/0 |
| Extra: 01862a3804a8f27ce792078f34a76e07f3abb9da77377c4c62c17f49e491e52092020900000001e49593ff00 | ||
1 output(s) for total of 34.785340692735 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1f1df307bcdd343eef4bc028c400ad0b3f2d1f12951a4e99238e680b1edd959a | 34.785340692735 | 7446 of 0 | <18> |
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": 6041,
"vin": [ {
"gen": {
"height": 5981
}
}
],
"vout": [ {
"amount": 34785340692735,
"target": {
"tagged_key": {
"key": "1f1df307bcdd343eef4bc028c400ad0b3f2d1f12951a4e99238e680b1edd959a",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 134, 42, 56, 4, 168, 242, 124, 231, 146, 7, 143, 52, 167, 110, 7, 243, 171, 185, 218, 119, 55, 124, 76, 98, 193, 127, 73, 228, 145, 229, 32, 146, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}