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: 78b0dc012abaaea8ef0f71df5d1c5f2523c01366df22ea5a1b19acec58621c20
Tx prefix hash: c26f0a48693bc78d5bc0623a972db0fe8256b17bbffdd7b83ca21708ca8d3e8b
Tx public key: 504bb1bb8c0012e3c743ad598a2626f057ee35b3a617d0fcf35d074371a5909a
| Timestamp: 1780697125 | Timestamp [UTC]: 2026-06-05 22:05:25 | Age [y:d:h:m:s]: 00:003:05:45:33 |
| Block: 6008 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1982 | RingCT/type: yes/0 |
| Extra: 01504bb1bb8c0012e3c743ad598a2626f057ee35b3a617d0fcf35d074371a5909a020900000001e49593ff00 | ||
1 output(s) for total of 34.783549347308 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4a4a00ca8df1f22514caa3e3a69c7e81ff282b9a7dce8ea52573491bf3597a33 | 34.783549347308 | 7475 of 0 | <88> |
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": 6068,
"vin": [ {
"gen": {
"height": 6008
}
}
],
"vout": [ {
"amount": 34783549347308,
"target": {
"tagged_key": {
"key": "4a4a00ca8df1f22514caa3e3a69c7e81ff282b9a7dce8ea52573491bf3597a33",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 80, 75, 177, 187, 140, 0, 18, 227, 199, 67, 173, 89, 138, 38, 38, 240, 87, 238, 53, 179, 166, 23, 208, 252, 243, 93, 7, 67, 113, 165, 144, 154, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}