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: a2c990ac85d354ef4011a6bd5f53c7b62c415660dfc485c52b16f046aecf0d86
Tx prefix hash: dffb3c43223d583f24f1c621c40501767d0b655d8388cd27c79a5876d6a53152
Tx public key: 3f8154f5890d6efd9d99420e1e4a3414474bb0dae63d5ed12349e0a3a1bda6df
| Timestamp: 1780863185 | Timestamp [UTC]: 2026-06-07 20:13:05 | Age [y:d:h:m:s]: 00:001:04:33:42 |
| Block: 7639 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 247 | RingCT/type: yes/0 |
| Extra: 013f8154f5890d6efd9d99420e1e4a3414474bb0dae63d5ed12349e0a3a1bda6df020900000003e49593ff00 | ||
1 output(s) for total of 34.675509737358 HMNY
| stealth address | amount | amount idx | tag |
| 00: 13e746e18f3270965fa7cd055216f79904018006f2cda38eb285dbfd3a41dfdb | 34.675509737358 | 9443 of 0 | <a8> |
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": 7699,
"vin": [ {
"gen": {
"height": 7639
}
}
],
"vout": [ {
"amount": 34675509737358,
"target": {
"tagged_key": {
"key": "13e746e18f3270965fa7cd055216f79904018006f2cda38eb285dbfd3a41dfdb",
"view_tag": "a8"
}
}
}
],
"extra": [ 1, 63, 129, 84, 245, 137, 13, 110, 253, 157, 153, 66, 14, 30, 74, 52, 20, 71, 75, 176, 218, 230, 61, 94, 209, 35, 73, 224, 163, 161, 189, 166, 223, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}