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: f591118a2397598af19d3829c6bf427a749ff43c7f6a83b19e768c27dc62d8dc
Tx prefix hash: db748d730d7abd14a3a983810ae83e255f6c927d8703e263797e5399f628c721
Tx public key: e37567b8803aceedf48dbbbf65752c904014fcabbbd4d947ecf37e98b38e4c4a
| Timestamp: 1779629454 | Timestamp [UTC]: 2026-05-24 13:30:54 | Age [y:d:h:m:s]: 00:015:12:05:03 |
| Block: 834 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7052 | RingCT/type: yes/0 |
| Extra: 01e37567b8803aceedf48dbbbf65752c904014fcabbbd4d947ecf37e98b38e4c4a020900000001ba6d17be00 | ||
1 output(s) for total of 35.128514737392 HMNY
| stealth address | amount | amount idx | tag |
| 00: 810ca8ec83caf290863a533824ec51d47a1f16b937caed6e0a55e40fee95e412 | 35.128514737392 | 966 of 0 | <e8> |
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": 894,
"vin": [ {
"gen": {
"height": 834
}
}
],
"vout": [ {
"amount": 35128514737392,
"target": {
"tagged_key": {
"key": "810ca8ec83caf290863a533824ec51d47a1f16b937caed6e0a55e40fee95e412",
"view_tag": "e8"
}
}
}
],
"extra": [ 1, 227, 117, 103, 184, 128, 58, 206, 237, 244, 141, 187, 191, 101, 117, 44, 144, 64, 20, 252, 171, 187, 212, 217, 71, 236, 243, 126, 152, 179, 142, 76, 74, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}