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: 400f5914a113aa8745cd19a86674e2a46c4dbbbcbc831650ebfe11a3f89140fc
Tx prefix hash: b79160bb81313669c0c2efbc74e2a7e8e41872a2f349731dc2ae5e713950c2d5
Tx public key: ef2c182a3b8c221d8093b8ecf96001cb9464e0a3a39d0e335251f4c98cffbf28
| Timestamp: 1780998836 | Timestamp [UTC]: 2026-06-09 09:53:56 | Age [y:d:h:m:s]: 00:007:22:11:25 |
| Block: 8402 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 343 | RingCT/type: yes/0 |
| Extra: 01ef2c182a3b8c221d8093b8ecf96001cb9464e0a3a39d0e335251f4c98cffbf28020900000001e49593ff00 | ||
1 output(s) for total of 34.625082879160 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1f81c904a90b1dd61efd59297986213f141fcb9427f5e51375b67dfec82feb57 | 34.625082879160 | 10386 of 0 | <1d> |
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": 8462,
"vin": [ {
"gen": {
"height": 8402
}
}
],
"vout": [ {
"amount": 34625082879160,
"target": {
"tagged_key": {
"key": "1f81c904a90b1dd61efd59297986213f141fcb9427f5e51375b67dfec82feb57",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 239, 44, 24, 42, 59, 140, 34, 29, 128, 147, 184, 236, 249, 96, 1, 203, 148, 100, 224, 163, 163, 157, 14, 51, 82, 81, 244, 201, 140, 255, 191, 40, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}