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: 5bc448b962281fd637c41c3a53934b53553cc357fe2bc29795f251e28a99629d
Tx prefix hash: e78f572ef13e939b233144478e6096f264e24c3ff341ac49420019c7b075f82a
Tx public key: 34c203011622cffc237c7517a78a1e4d0ce8ae54a32d1c38ef01473763617849
| Timestamp: 1780985844 | Timestamp [UTC]: 2026-06-09 06:17:24 | Age [y:d:h:m:s]: 00:000:07:20:12 |
| Block: 8140 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 461 | RingCT/type: yes/0 |
| Extra: 0134c203011622cffc237c7517a78a1e4d0ce8ae54a32d1c38ef01473763617849020900000003e49593ff00 | ||
1 output(s) for total of 34.642390251149 HMNY
| stealth address | amount | amount idx | tag |
| 00: 990de509c9fd71da6c66a2c379d72530f913c45867ebdd093b68f5e94f990625 | 34.642390251149 | 10080 of 0 | <34> |
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": 8200,
"vin": [ {
"gen": {
"height": 8140
}
}
],
"vout": [ {
"amount": 34642390251149,
"target": {
"tagged_key": {
"key": "990de509c9fd71da6c66a2c379d72530f913c45867ebdd093b68f5e94f990625",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 52, 194, 3, 1, 22, 34, 207, 252, 35, 124, 117, 23, 167, 138, 30, 77, 12, 232, 174, 84, 163, 45, 28, 56, 239, 1, 71, 55, 99, 97, 120, 73, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}