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: 7d5eb7dc8e6174415a86c4194f8c654e41ff7a7d7d84de022c843c958f34d0a1
Tx prefix hash: 2464b0e13ad323643acda5969f1a45418e7da92b1996f797f9268c91dfb60f26
Tx public key: be04a9f6502e700fbac7a02faaf6dac891dea023f27dbca3f054aeaa69537e2f
| Timestamp: 1780716595 | Timestamp [UTC]: 2026-06-06 03:29:55 | Age [y:d:h:m:s]: 00:002:22:06:02 |
| Block: 6201 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1685 | RingCT/type: yes/0 |
| Extra: 01be04a9f6502e700fbac7a02faaf6dac891dea023f27dbca3f054aeaa69537e2f020900000001e49593ff00 | ||
1 output(s) for total of 34.770747231019 HMNY
| stealth address | amount | amount idx | tag |
| 00: 88761fb2d6629c13c5c3fea4e27130ed29a64cdb017e853581592c97a2a34aca | 34.770747231019 | 7680 of 0 | <89> |
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": 6261,
"vin": [ {
"gen": {
"height": 6201
}
}
],
"vout": [ {
"amount": 34770747231019,
"target": {
"tagged_key": {
"key": "88761fb2d6629c13c5c3fea4e27130ed29a64cdb017e853581592c97a2a34aca",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 190, 4, 169, 246, 80, 46, 112, 15, 186, 199, 160, 47, 170, 246, 218, 200, 145, 222, 160, 35, 242, 125, 188, 163, 240, 84, 174, 170, 105, 83, 126, 47, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}