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: 10452fb175514c7c817fdb7a3b20120a97020e10f7a2e292bf9d74eeeace512b
Tx prefix hash: 7c1fd6c19d81b950f73c2a959c7c11349c5a3d0f7d90195ba7ddddfafe91c8cc
Tx public key: 88afc5f12305343dc2d51542f91cb6454ff99d3675ddee10352ee27d519a8c68
| Timestamp: 1780809184 | Timestamp [UTC]: 2026-06-07 05:13:04 | Age [y:d:h:m:s]: 00:001:21:27:32 |
| Block: 6996 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 900 | RingCT/type: yes/0 |
| Extra: 0188afc5f12305343dc2d51542f91cb6454ff99d3675ddee10352ee27d519a8c68020900000002e49593ff00 | ||
1 output(s) for total of 34.718062784625 HMNY
| stealth address | amount | amount idx | tag |
| 00: 574b0731e48c4718a7238daa303a89182ab9bab32c3c7469b8fc4fa5a0ea8531 | 34.718062784625 | 8628 of 0 | <b5> |
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": 7056,
"vin": [ {
"gen": {
"height": 6996
}
}
],
"vout": [ {
"amount": 34718062784625,
"target": {
"tagged_key": {
"key": "574b0731e48c4718a7238daa303a89182ab9bab32c3c7469b8fc4fa5a0ea8531",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 136, 175, 197, 241, 35, 5, 52, 61, 194, 213, 21, 66, 249, 28, 182, 69, 79, 249, 157, 54, 117, 221, 238, 16, 53, 46, 226, 125, 81, 154, 140, 104, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}