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: a9ce82a3d2329db1f4b4ee1c70666b929581cd09114e06a6b784eb5204967ad4
Tx prefix hash: 3cc93e699c34c0e27e66acd0ea1811111a243e7ef28d8691de18578454f27673
Tx public key: db5dfcc032ef0861d42c31e031479ce81ab01a98d1b04c1dc7f8d0c5373000cd
| Timestamp: 1780982889 | Timestamp [UTC]: 2026-06-09 05:28:09 | Age [y:d:h:m:s]: 00:000:07:09:36 |
| Block: 8074 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 500 | RingCT/type: yes/0 |
| Extra: 01db5dfcc032ef0861d42c31e031479ce81ab01a98d1b04c1dc7f8d0c5373000cd020900000001e49593ff00 | ||
1 output(s) for total of 34.646751487444 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3f2f8c791139203d39b99e55bd9dd8506588f78801a5f12d3e2d77662420853 | 34.646751487444 | 10004 of 0 | <db> |
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": 8134,
"vin": [ {
"gen": {
"height": 8074
}
}
],
"vout": [ {
"amount": 34646751487444,
"target": {
"tagged_key": {
"key": "c3f2f8c791139203d39b99e55bd9dd8506588f78801a5f12d3e2d77662420853",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 219, 93, 252, 192, 50, 239, 8, 97, 212, 44, 49, 224, 49, 71, 156, 232, 26, 176, 26, 152, 209, 176, 76, 29, 199, 248, 208, 197, 55, 48, 0, 205, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}