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: 91d69d1a81077a358117c6642068e65bc14c71901598634269f93f8beb4404b2
Tx prefix hash: 2445d84affb16acc96142d755f0e807bc7d2df778df1a737d235438af15d1f5a
Tx public key: 2494b4f794e63428cb6b0b7a3a244e50c42e39a3494da8ff85b2c43d8af88339
| Timestamp: 1779850953 | Timestamp [UTC]: 2026-05-27 03:02:33 | Age [y:d:h:m:s]: 00:012:23:47:15 |
| Block: 2528 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5372 | RingCT/type: yes/0 |
| Extra: 012494b4f794e63428cb6b0b7a3a244e50c42e39a3494da8ff85b2c43d8af8833902090000000226697be300 | ||
1 output(s) for total of 35.015195859507 HMNY
| stealth address | amount | amount idx | tag |
| 00: 41cac9477ae08f765177fe9ccdd634eddf89987e2f8ef8078ed6a2691d487728 | 35.015195859507 | 2976 of 0 | <7d> |
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": 2588,
"vin": [ {
"gen": {
"height": 2528
}
}
],
"vout": [ {
"amount": 35015195859507,
"target": {
"tagged_key": {
"key": "41cac9477ae08f765177fe9ccdd634eddf89987e2f8ef8078ed6a2691d487728",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 36, 148, 180, 247, 148, 230, 52, 40, 203, 107, 11, 122, 58, 36, 78, 80, 196, 46, 57, 163, 73, 77, 168, 255, 133, 178, 196, 61, 138, 248, 131, 57, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}