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: a31de4c3a4bae41ddec5fa23cb89868b44a2361e2a8de95ed6f1b675ac8f3d2b
Tx prefix hash: dc5ea413d3fef137d8cdb95968f86584d250c34874609012ad82e05d14af59e9
Tx public key: ec4593c462fcf9a4aae617e14b7d58295d9e792c0bec049e4de5be1df22b54bd
| Timestamp: 1780822378 | Timestamp [UTC]: 2026-06-07 08:52:58 | Age [y:d:h:m:s]: 00:001:15:53:49 |
| Block: 7202 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 684 | RingCT/type: yes/0 |
| Extra: 01ec4593c462fcf9a4aae617e14b7d58295d9e792c0bec049e4de5be1df22b54bd020900000002e49593ff00 | ||
1 output(s) for total of 34.704424244565 HMNY
| stealth address | amount | amount idx | tag |
| 00: c7263c215f5edc1b22a7aeb6500b76282a547a688908ffb2b47abd3081daedd7 | 34.704424244565 | 8870 of 0 | <fe> |
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": 7262,
"vin": [ {
"gen": {
"height": 7202
}
}
],
"vout": [ {
"amount": 34704424244565,
"target": {
"tagged_key": {
"key": "c7263c215f5edc1b22a7aeb6500b76282a547a688908ffb2b47abd3081daedd7",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 236, 69, 147, 196, 98, 252, 249, 164, 170, 230, 23, 225, 75, 125, 88, 41, 93, 158, 121, 44, 11, 236, 4, 158, 77, 229, 190, 29, 242, 43, 84, 189, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}