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: b622163726d1e95f2c57f99ee4fb4e3318099b0f3287de998739e39a18ce751d
Tx prefix hash: de59c994db8bad2a64c456ea69f28ac8535acbc48270f0e0f70bd0dd345b4c4c
Tx public key: a58bdea992577be9a3f12befa738337ef19326dc875e48ae691d76dce9bbf87e
| Timestamp: 1780853923 | Timestamp [UTC]: 2026-06-07 17:38:43 | Age [y:d:h:m:s]: 00:001:10:00:07 |
| Block: 7556 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 386 | RingCT/type: yes/0 |
| Extra: 01a58bdea992577be9a3f12befa738337ef19326dc875e48ae691d76dce9bbf87e020900000004e49593ff00 | ||
1 output(s) for total of 34.680999654881 HMNY
| stealth address | amount | amount idx | tag |
| 00: 057640487ff5183cbf6f74de91e14f414f8d6922b7824d12948b392d7295545f | 34.680999654881 | 9328 of 0 | <20> |
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": 7616,
"vin": [ {
"gen": {
"height": 7556
}
}
],
"vout": [ {
"amount": 34680999654881,
"target": {
"tagged_key": {
"key": "057640487ff5183cbf6f74de91e14f414f8d6922b7824d12948b392d7295545f",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 165, 139, 222, 169, 146, 87, 123, 233, 163, 241, 43, 239, 167, 56, 51, 126, 241, 147, 38, 220, 135, 94, 72, 174, 105, 29, 118, 220, 233, 187, 248, 126, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}