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: f16219f84a567096846cde8223aef8dd94d11db8e8fe4e042e0ea7ce02ed488c
Tx prefix hash: 72518e997238429b8cc2baee5a63c5c94d1d4aa9ee9f0545e0fe26f2622ebe02
Tx public key: b5a3c3a36cb6205c76814854f435ba2c2efe65a14fba1a092e4685ccf52a6419
| Timestamp: 1780323164 | Timestamp [UTC]: 2026-06-01 14:12:44 | Age [y:d:h:m:s]: 00:008:02:56:19 |
| Block: 5066 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3668 | RingCT/type: yes/0 |
| Extra: 01b5a3c3a36cb6205c76814854f435ba2c2efe65a14fba1a092e4685ccf52a641902090000002226697be300 | ||
1 output(s) for total of 34.846101967668 HMNY
| stealth address | amount | amount idx | tag |
| 00: d3049fe863799f32e7e2ec9a90d9cb9c72b6f27f86ff513762e065e36ae02513 | 34.846101967668 | 6441 of 0 | <53> |
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": 5126,
"vin": [ {
"gen": {
"height": 5066
}
}
],
"vout": [ {
"amount": 34846101967668,
"target": {
"tagged_key": {
"key": "d3049fe863799f32e7e2ec9a90d9cb9c72b6f27f86ff513762e065e36ae02513",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 181, 163, 195, 163, 108, 182, 32, 92, 118, 129, 72, 84, 244, 53, 186, 44, 46, 254, 101, 161, 79, 186, 26, 9, 46, 70, 133, 204, 245, 42, 100, 25, 2, 9, 0, 0, 0, 34, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}