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: 4913a14566be98013a0b6de08c1ad2b9b9b56d19822cabeebc98e8a3d9560490
Tx prefix hash: 7ed6aeff93549ce36805564fc83930447f99f6f43b1250a9c716893e25e980fe
Tx public key: 92dd6525215cfc4ddf5e6dc30ed2c92a93c30625ee40c547a053aaf53031202d
| Timestamp: 1780400304 | Timestamp [UTC]: 2026-06-02 11:38:24 | Age [y:d:h:m:s]: 00:006:13:08:23 |
| Block: 5275 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2611 | RingCT/type: yes/0 |
| Extra: 0192dd6525215cfc4ddf5e6dc30ed2c92a93c30625ee40c547a053aaf53031202d02090000000226697be300 | ||
1 output(s) for total of 34.832213816791 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6c81ab5b8b3a33a721e48478da32a6c976f35801d277e1e4b52b5c3d078028e | 34.832213816791 | 6688 of 0 | <60> |
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": 5335,
"vin": [ {
"gen": {
"height": 5275
}
}
],
"vout": [ {
"amount": 34832213816791,
"target": {
"tagged_key": {
"key": "b6c81ab5b8b3a33a721e48478da32a6c976f35801d277e1e4b52b5c3d078028e",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 146, 221, 101, 37, 33, 92, 252, 77, 223, 94, 109, 195, 14, 210, 201, 42, 147, 195, 6, 37, 238, 64, 197, 71, 160, 83, 170, 245, 48, 49, 32, 45, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}