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: 056dad518857ec858ea9aca2ef18365e61a1516539e97ca7b9d106731459d29f
Tx prefix hash: 4fbd94694956de50c47fc40db549dc70ff065eabf03937d1c7141e71bb8791f2
Tx public key: f3bfe7b833bf28d3c9c57b787f67c2d94ea03e1241545159e0b4be9ff72c0b0d
| Timestamp: 1780833916 | Timestamp [UTC]: 2026-06-07 12:05:16 | Age [y:d:h:m:s]: 00:001:11:13:37 |
| Block: 7378 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 508 | RingCT/type: yes/0 |
| Extra: 01f3bfe7b833bf28d3c9c57b787f67c2d94ea03e1241545159e0b4be9ff72c0b0d020900000002e49593ff00 | ||
1 output(s) for total of 34.692776143901 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4b274d23329d6b5e685883e2d66e84cc099111e32b7f8ab6af3ea9e27dd9aa06 | 34.692776143901 | 9084 of 0 | <db> |
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": 7438,
"vin": [ {
"gen": {
"height": 7378
}
}
],
"vout": [ {
"amount": 34692776143901,
"target": {
"tagged_key": {
"key": "4b274d23329d6b5e685883e2d66e84cc099111e32b7f8ab6af3ea9e27dd9aa06",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 243, 191, 231, 184, 51, 191, 40, 211, 201, 197, 123, 120, 127, 103, 194, 217, 78, 160, 62, 18, 65, 84, 81, 89, 224, 180, 190, 159, 247, 44, 11, 13, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}