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: 134c27cc6d0cf93d10a9bf55ae2c1b07f0e026d8a82c9993b97c9a33fa36d1f1
Tx prefix hash: f9139090e561a63ae0cb92d983c34ebb39eaa44a1a51d88bc45788b5562bcbd4
Tx public key: c559a4b617aa3e9836ee5e0d94d7646ee71edd4999150470982367f9bc32888d
| Timestamp: 1780834814 | Timestamp [UTC]: 2026-06-07 12:20:14 | Age [y:d:h:m:s]: 00:009:20:02:05 |
| Block: 7393 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1352 | RingCT/type: yes/0 |
| Extra: 01c559a4b617aa3e9836ee5e0d94d7646ee71edd4999150470982367f9bc32888d020900000003e49593ff00 | ||
1 output(s) for total of 34.691783588866 HMNY
| stealth address | amount | amount idx | tag |
| 00: b58f84f94a1443c6c92bf3bb93ce04e3062aa136108e9d3008f2467d9863803f | 34.691783588866 | 9103 of 0 | <db> |
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": 7453,
"vin": [ {
"gen": {
"height": 7393
}
}
],
"vout": [ {
"amount": 34691783588866,
"target": {
"tagged_key": {
"key": "b58f84f94a1443c6c92bf3bb93ce04e3062aa136108e9d3008f2467d9863803f",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 197, 89, 164, 182, 23, 170, 62, 152, 54, 238, 94, 13, 148, 215, 100, 110, 231, 30, 221, 73, 153, 21, 4, 112, 152, 35, 103, 249, 188, 50, 136, 141, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}