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: 8b9c39838e964f3293f8275bec9ff4d4921d1e71ac9b552e203e96924242a95f
Tx prefix hash: 101359f8cd3133444c3fae5a0fe71ef33e2fb6fbb7b0dd014c91301c8df194cd
Tx public key: 644b2961f07f12e3103e9698dc011c92d3c8704b28547f713eeb0ff6497ff3ca
| Timestamp: 1779962328 | Timestamp [UTC]: 2026-05-28 09:58:48 | Age [y:d:h:m:s]: 00:011:13:20:05 |
| Block: 3775 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4111 | RingCT/type: yes/0 |
| Extra: 01644b2961f07f12e3103e9698dc011c92d3c8704b28547f713eeb0ff6497ff3ca02090000000226697be300 | ||
1 output(s) for total of 34.932012369969 HMNY
| stealth address | amount | amount idx | tag |
| 00: acb58581558e6448076dc2d17fdb21c88a0290ef0b2a44c24430c9ee6da761be | 34.932012369969 | 4582 of 0 | <8b> |
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": 3835,
"vin": [ {
"gen": {
"height": 3775
}
}
],
"vout": [ {
"amount": 34932012369969,
"target": {
"tagged_key": {
"key": "acb58581558e6448076dc2d17fdb21c88a0290ef0b2a44c24430c9ee6da761be",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 100, 75, 41, 97, 240, 127, 18, 227, 16, 62, 150, 152, 220, 1, 28, 146, 211, 200, 112, 75, 40, 84, 127, 113, 62, 235, 15, 246, 73, 127, 243, 202, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}