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: c1aedd0b6d2c2c532a2c81761b382aabcf3c6613a1bbf03c2e2d8532c82afd40
Tx prefix hash: 7f8bcbe16e0796dc907828d582412c168691fdb5a72fb5611b09b3e51c546bf3
Tx public key: 349374842b01050af36dd780d4ce8c239c23259354640f2dc264e8fa439f91da
| Timestamp: 1780745998 | Timestamp [UTC]: 2026-06-06 11:39:58 | Age [y:d:h:m:s]: 00:003:05:29:05 |
| Block: 6453 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2281 | RingCT/type: yes/0 |
| Extra: 01349374842b01050af36dd780d4ce8c239c23259354640f2dc264e8fa439f91da020900000003e49593ff00 | ||
1 output(s) for total of 34.754038606749 HMNY
| stealth address | amount | amount idx | tag |
| 00: f91d73bf70ca79b76d4909f024dc1949e13e2449ccfc9507c38122bce6aa70f3 | 34.754038606749 | 7946 of 0 | <b1> |
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": 6513,
"vin": [ {
"gen": {
"height": 6453
}
}
],
"vout": [ {
"amount": 34754038606749,
"target": {
"tagged_key": {
"key": "f91d73bf70ca79b76d4909f024dc1949e13e2449ccfc9507c38122bce6aa70f3",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 52, 147, 116, 132, 43, 1, 5, 10, 243, 109, 215, 128, 212, 206, 140, 35, 156, 35, 37, 147, 84, 100, 15, 45, 194, 100, 232, 250, 67, 159, 145, 218, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}