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: 866ac353abc73e2f9d3dc464ac5d4158f2616aec9f5153e10ef81a5fe120b179
Tx prefix hash: d8da0e69881f3885662eaca9aa17998ad04b527d9b6945849c896cce9bbebe43
Tx public key: e71f7284a7f9f50c299ded8ebf479d84b72a9b75952d87b610188ab6b073ecf7
| Timestamp: 1780072616 | Timestamp [UTC]: 2026-05-29 16:36:56 | Age [y:d:h:m:s]: 00:010:08:59:01 |
| Block: 4662 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3224 | RingCT/type: yes/0 |
| Extra: 01e71f7284a7f9f50c299ded8ebf479d84b72a9b75952d87b610188ab6b073ecf702090000000426697be300 | ||
1 output(s) for total of 34.872963661987 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b0cf8881a26f2b0871695f6b8f0661ad41a42ef30d762dae8139d5faedb35b6 | 34.872963661987 | 5855 of 0 | <ba> |
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": 4722,
"vin": [ {
"gen": {
"height": 4662
}
}
],
"vout": [ {
"amount": 34872963661987,
"target": {
"tagged_key": {
"key": "2b0cf8881a26f2b0871695f6b8f0661ad41a42ef30d762dae8139d5faedb35b6",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 231, 31, 114, 132, 167, 249, 245, 12, 41, 157, 237, 142, 191, 71, 157, 132, 183, 42, 155, 117, 149, 45, 135, 182, 16, 24, 138, 182, 176, 115, 236, 247, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}