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: 40b50ff9221b3e528d6b33f4a1e994e105a1361eb4b122564c76cefed6245678
Tx prefix hash: 0286215fef1f9bf60f59b4213eb884fc5a507fb88dc3e4293e3745b81512788a
Tx public key: 6dfc213097b6c9a376e3af6de041c839b8960a86eb4fcb8a80d621dd7d1df02a
| Timestamp: 1780833438 | Timestamp [UTC]: 2026-06-07 11:57:18 | Age [y:d:h:m:s]: 00:001:09:14:49 |
| Block: 7369 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 517 | RingCT/type: yes/0 |
| Extra: 016dfc213097b6c9a376e3af6de041c839b8960a86eb4fcb8a80d621dd7d1df02a020900000001e49593ff00 | ||
1 output(s) for total of 34.693371690553 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2962cd79c1e8cde9808353e7ffaadf64306975b02a711cf9e48c87ce7797adeb | 34.693371690553 | 9073 of 0 | <31> |
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": 7429,
"vin": [ {
"gen": {
"height": 7369
}
}
],
"vout": [ {
"amount": 34693371690553,
"target": {
"tagged_key": {
"key": "2962cd79c1e8cde9808353e7ffaadf64306975b02a711cf9e48c87ce7797adeb",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 109, 252, 33, 48, 151, 182, 201, 163, 118, 227, 175, 109, 224, 65, 200, 57, 184, 150, 10, 134, 235, 79, 203, 138, 128, 214, 33, 221, 125, 29, 240, 42, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}