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: ac72bbed9da20f3197b0c632fc386171bb11a65c3e19b3697ebf8db6bbf09821
Tx prefix hash: 70841514c7848d2687a6417f5d8815398fc7a83ab71995f45254e1cd78d3de58
Tx public key: 0aa621ec6b5a39db017dccd3bdc4e2149c0e2c262fb8d98cbd82667a9419c50f
| Timestamp: 1780046935 | Timestamp [UTC]: 2026-05-29 09:28:55 | Age [y:d:h:m:s]: 00:010:13:49:58 |
| Block: 4353 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3533 | RingCT/type: yes/0 |
| Extra: 010aa621ec6b5a39db017dccd3bdc4e2149c0e2c262fb8d98cbd82667a9419c50f02090000000426697be300 | ||
1 output(s) for total of 34.893522843454 HMNY
| stealth address | amount | amount idx | tag |
| 00: ba9dc6ea95ddcf51d27241b48d3e7e3d3c6a82454e76d1b30ee204500e74adaa | 34.893522843454 | 5444 of 0 | <d6> |
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": 4413,
"vin": [ {
"gen": {
"height": 4353
}
}
],
"vout": [ {
"amount": 34893522843454,
"target": {
"tagged_key": {
"key": "ba9dc6ea95ddcf51d27241b48d3e7e3d3c6a82454e76d1b30ee204500e74adaa",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 10, 166, 33, 236, 107, 90, 57, 219, 1, 125, 204, 211, 189, 196, 226, 20, 156, 14, 44, 38, 47, 184, 217, 140, 189, 130, 102, 122, 148, 25, 197, 15, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}