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: 8575cb9e2e0f9e8f420ea939f5f8907d0eaf5dbef1978222820031832754c3c2
Tx prefix hash: b7168e9c9939c23de3bb7d68aff5fe0dcf90cd2238984ebe31da65b4177273d9
Tx public key: 35f9e4234aeda646fa3bfef7aa798e9eb69bfa4b026465d1f5e805decd341761
| Timestamp: 1780017836 | Timestamp [UTC]: 2026-05-29 01:23:56 | Age [y:d:h:m:s]: 00:011:01:16:40 |
| Block: 4126 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3771 | RingCT/type: yes/0 |
| Extra: 0135f9e4234aeda646fa3bfef7aa798e9eb69bfa4b026465d1f5e805decd34176102090000000126697be300 | ||
1 output(s) for total of 34.911249912606 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e09931abf4036f3a3bd52b1f118fd25480a8e0267a8ee698a8c9c51cebfa4c6 | 34.911249912606 | 5149 of 0 | <ed> |
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": 4186,
"vin": [ {
"gen": {
"height": 4126
}
}
],
"vout": [ {
"amount": 34911249912606,
"target": {
"tagged_key": {
"key": "4e09931abf4036f3a3bd52b1f118fd25480a8e0267a8ee698a8c9c51cebfa4c6",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 53, 249, 228, 35, 74, 237, 166, 70, 250, 59, 254, 247, 170, 121, 142, 158, 182, 155, 250, 75, 2, 100, 101, 209, 245, 232, 5, 222, 205, 52, 23, 97, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}