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: 21d89a9fe8a3ac8b6b25dbe1600f3ed23d6969c7ad5e87aa34e68320ed07a145
Tx prefix hash: db399cf2667ca0f1f27c81dc3720f1a594a69d01593fc54f73ab5e363ccf2bb4
Tx public key: 654dab4356f9286c016de953784cb0d3fc6128f2a6b26a3ab37bf2b99a138599
| Timestamp: 1780019858 | Timestamp [UTC]: 2026-05-29 01:57:38 | Age [y:d:h:m:s]: 00:010:23:38:19 |
| Block: 4138 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3748 | RingCT/type: yes/0 |
| Extra: 01654dab4356f9286c016de953784cb0d3fc6128f2a6b26a3ab37bf2b99a13859902090000000626697be300 | ||
1 output(s) for total of 34.907834925765 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9827bb9af0c380cd986acba488825af25d112b2c8e5de0180b48e7cd62d2eb25 | 34.907834925765 | 5169 of 0 | <bc> |
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": 4198,
"vin": [ {
"gen": {
"height": 4138
}
}
],
"vout": [ {
"amount": 34907834925765,
"target": {
"tagged_key": {
"key": "9827bb9af0c380cd986acba488825af25d112b2c8e5de0180b48e7cd62d2eb25",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 101, 77, 171, 67, 86, 249, 40, 108, 1, 109, 233, 83, 120, 76, 176, 211, 252, 97, 40, 242, 166, 178, 106, 58, 179, 123, 242, 185, 154, 19, 133, 153, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}