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: fa74ef947b1f675ebdba9ac2d81c64aec1b0796341480eb9d114a569779fd300
Tx prefix hash: a9eabb41a07a804d5a5c408de447cd6c47af94bf13d11b6abfe82ca5dcf48a2a
Tx public key: 511998292a2511d52ea693e6832ac1217e34121628569e9fe6b47cb1224919f5
| Timestamp: 1780809836 | Timestamp [UTC]: 2026-06-07 05:23:56 | Age [y:d:h:m:s]: 00:001:19:22:51 |
| Block: 7006 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 880 | RingCT/type: yes/0 |
| Extra: 01511998292a2511d52ea693e6832ac1217e34121628569e9fe6b47cb1224919f5020900000001e49593ff00 | ||
1 output(s) for total of 34.717400595813 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61938c252fc9e5866438db2490785d6a25f9a54a396e5779c74db1d13f25e8f3 | 34.717400595813 | 8640 of 0 | <13> |
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": 7066,
"vin": [ {
"gen": {
"height": 7006
}
}
],
"vout": [ {
"amount": 34717400595813,
"target": {
"tagged_key": {
"key": "61938c252fc9e5866438db2490785d6a25f9a54a396e5779c74db1d13f25e8f3",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 81, 25, 152, 41, 42, 37, 17, 213, 46, 166, 147, 230, 131, 42, 193, 33, 126, 52, 18, 22, 40, 86, 158, 159, 230, 180, 124, 177, 34, 73, 25, 245, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}