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: 012286ee34adb74926472f1db2862379ed09a6c9afb4fcba2c6967426b48f1e5
Tx prefix hash: c32faceef1b6fcc305fc0759896968ad0d79704a8e7f00cf8a1505bf94bb065a
Tx public key: 57f3d5caa9058d1e0a405e6e9058b4ca33bef61148eb7a08c4393c61dcb9fe40
| Timestamp: 1780984068 | Timestamp [UTC]: 2026-06-09 05:47:48 | Age [y:d:h:m:s]: 00:000:10:11:56 |
| Block: 8106 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 585 | RingCT/type: yes/0 |
| Extra: 0157f3d5caa9058d1e0a405e6e9058b4ca33bef61148eb7a08c4393c61dcb9fe40020900000002e49593ff00 | ||
1 output(s) for total of 34.644636880070 HMNY
| stealth address | amount | amount idx | tag |
| 00: a7995f64f698a183820b80f591934386241dd327d03d25a3771ab86f0891b509 | 34.644636880070 | 10040 of 0 | <b2> |
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": 8166,
"vin": [ {
"gen": {
"height": 8106
}
}
],
"vout": [ {
"amount": 34644636880070,
"target": {
"tagged_key": {
"key": "a7995f64f698a183820b80f591934386241dd327d03d25a3771ab86f0891b509",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 87, 243, 213, 202, 169, 5, 141, 30, 10, 64, 94, 110, 144, 88, 180, 202, 51, 190, 246, 17, 72, 235, 122, 8, 196, 57, 60, 97, 220, 185, 254, 64, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}