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: 5302a92b87c43fced08d9506fd2e9b7ab2c8c7dbbd5a7ad15f68ecc11bd320c0
Tx prefix hash: df0375f864a0cd4da98a328c9c8c6a536d74701803a7de4c17366ff96a40a169
Tx public key: 45bf491ae22be715248593ac68de6476261340400f8a4f2e2bafcb91ce5b4b66
| Timestamp: 1781022419 | Timestamp [UTC]: 2026-06-09 16:26:59 | Age [y:d:h:m:s]: 00:006:06:23:49 |
| Block: 8707 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 38 | RingCT/type: yes/0 |
| Extra: 0145bf491ae22be715248593ac68de6476261340400f8a4f2e2bafcb91ce5b4b66020900000001e49593ff00 | ||
1 output(s) for total of 34.604945875918 HMNY
| stealth address | amount | amount idx | tag |
| 00: d743a7df246c32a19933935379f130a69cef8c1f9b0a93d1feb0a4f374a87509 | 34.604945875918 | 10767 of 0 | <62> |
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": 8767,
"vin": [ {
"gen": {
"height": 8707
}
}
],
"vout": [ {
"amount": 34604945875918,
"target": {
"tagged_key": {
"key": "d743a7df246c32a19933935379f130a69cef8c1f9b0a93d1feb0a4f374a87509",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 69, 191, 73, 26, 226, 43, 231, 21, 36, 133, 147, 172, 104, 222, 100, 118, 38, 19, 64, 64, 15, 138, 79, 46, 43, 175, 203, 145, 206, 91, 75, 102, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}