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: d2db26c50e14cd1614c92c9633b2bcd1be22d5703369ad5b25b270bfa4a06e40
Tx prefix hash: 4522bd56de655f3ec5aa9922a2c4aaedbba3f9f794b29adc269e7a14050149ce
Tx public key: 466729f611ce4352e2d4076e361b79a01858438ad6f415d6b99b88cb74b3258d
| Timestamp: 1780730483 | Timestamp [UTC]: 2026-06-06 07:21:23 | Age [y:d:h:m:s]: 00:002:15:57:30 |
| Block: 6310 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1576 | RingCT/type: yes/0 |
| Extra: 01466729f611ce4352e2d4076e361b79a01858438ad6f415d6b99b88cb74b3258d020900000002e49593ff00 | ||
1 output(s) for total of 34.763519102366 HMNY
| stealth address | amount | amount idx | tag |
| 00: 95beeb04273fe53ce3525db6b9ba24731c817aa7bcb8fc265ad410a22bb89aa4 | 34.763519102366 | 7795 of 0 | <82> |
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": 6370,
"vin": [ {
"gen": {
"height": 6310
}
}
],
"vout": [ {
"amount": 34763519102366,
"target": {
"tagged_key": {
"key": "95beeb04273fe53ce3525db6b9ba24731c817aa7bcb8fc265ad410a22bb89aa4",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 70, 103, 41, 246, 17, 206, 67, 82, 226, 212, 7, 110, 54, 27, 121, 160, 24, 88, 67, 138, 214, 244, 21, 214, 185, 155, 136, 203, 116, 179, 37, 141, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}