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: b131c45f4b81c2f3b5cf060893ca9e9fab84344ac8d728b54aac5caacb2cf8de
Tx prefix hash: 73c976620a1190e875d9c0545cc99011d5af517ad199e0003d047d43958f88a8
Tx public key: ab5f103249c2dd99c6103148a9cb1118111903f90ef666f4c362a2ae54421af9
| Timestamp: 1781024483 | Timestamp [UTC]: 2026-06-09 17:01:23 | Age [y:d:h:m:s]: 00:005:21:30:16 |
| Block: 8727 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 18 | RingCT/type: yes/0 |
| Extra: 01ab5f103249c2dd99c6103148a9cb1118111903f90ef666f4c362a2ae54421af9020900000003e49593ff00 | ||
1 output(s) for total of 34.603625825913 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9577524324bc55b458588ef37158a51db8d4bbba235fa683f928fdeb4b2f28fb | 34.603625825913 | 10795 of 0 | <7a> |
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": 8787,
"vin": [ {
"gen": {
"height": 8727
}
}
],
"vout": [ {
"amount": 34603625825913,
"target": {
"tagged_key": {
"key": "9577524324bc55b458588ef37158a51db8d4bbba235fa683f928fdeb4b2f28fb",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 171, 95, 16, 50, 73, 194, 221, 153, 198, 16, 49, 72, 169, 203, 17, 24, 17, 25, 3, 249, 14, 246, 102, 244, 195, 98, 162, 174, 84, 66, 26, 249, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}