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: 2e476b925477da9715cda7e92b0fa58d479b7d38899bc9add7dfcb5db4d82851
Tx prefix hash: db1615fdf71f567939565de6b914f7ae1cdf18cdb0a417e699062200eef68fe6
Tx public key: 8c5718428b20199a09c2c175de8f7f9d2f82ee360a22d5ee20405e60b9fc9919
| Timestamp: 1779946203 | Timestamp [UTC]: 2026-05-28 05:30:03 | Age [y:d:h:m:s]: 00:011:22:08:47 |
| Block: 3562 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4379 | RingCT/type: yes/0 |
| Extra: 018c5718428b20199a09c2c175de8f7f9d2f82ee360a22d5ee20405e60b9fc991902090000000326697be300 | ||
1 output(s) for total of 34.977492129734 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56381fce93d0740fa11a6c87b40e8b3e180b7161f60bc9bd0e939345d5a16be5 | 34.977492129734 | 4296 of 0 | <8f> |
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": 3622,
"vin": [ {
"gen": {
"height": 3562
}
}
],
"vout": [ {
"amount": 34977492129734,
"target": {
"tagged_key": {
"key": "56381fce93d0740fa11a6c87b40e8b3e180b7161f60bc9bd0e939345d5a16be5",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 140, 87, 24, 66, 139, 32, 25, 154, 9, 194, 193, 117, 222, 143, 127, 157, 47, 130, 238, 54, 10, 34, 213, 238, 32, 64, 94, 96, 185, 252, 153, 25, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}