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: 5b1165e302b8efc12d6e2fc87aa8c5c063d91f919aa31a0ac4c3d8fbaa1a9023
Tx prefix hash: 319cae3daa5f5122ed707b932ab9381dcd858433792efd8c852511e707025677
Tx public key: 3daeedc26cdabd42f1464f351e3d18b151365d73069167997e158ed8b24a45ba
| Timestamp: 1780981689 | Timestamp [UTC]: 2026-06-09 05:08:09 | Age [y:d:h:m:s]: 00:000:08:29:27 |
| Block: 8045 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 556 | RingCT/type: yes/0 |
| Extra: 013daeedc26cdabd42f1464f351e3d18b151365d73069167997e158ed8b24a45ba020900000001e49593ff00 | ||
1 output(s) for total of 34.648667961863 HMNY
| stealth address | amount | amount idx | tag |
| 00: db1e4e407b99c2eeaeaaf9a94cadd3452501315ccee09211467218d7808a27b0 | 34.648667961863 | 9971 of 0 | <2d> |
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": 8105,
"vin": [ {
"gen": {
"height": 8045
}
}
],
"vout": [ {
"amount": 34648667961863,
"target": {
"tagged_key": {
"key": "db1e4e407b99c2eeaeaaf9a94cadd3452501315ccee09211467218d7808a27b0",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 61, 174, 237, 194, 108, 218, 189, 66, 241, 70, 79, 53, 30, 61, 24, 177, 81, 54, 93, 115, 6, 145, 103, 153, 126, 21, 142, 216, 178, 74, 69, 186, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}