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: 7273f4aca471b72bfbdf5273349918e6db7669e4c7c7000547079c1e3834697a
Tx prefix hash: 2b4b21bf3d76e71f7d304c921a3fb3bf6b2449f4015958d449a76fe46da062e6
Tx public key: 6b84014e439dd5fcfabeb69242971a9d392db5678da472f21475a26f42dd34c2
| Timestamp: 1780984282 | Timestamp [UTC]: 2026-06-09 05:51:22 | Age [y:d:h:m:s]: 00:000:10:08:22 |
| Block: 8110 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 581 | RingCT/type: yes/0 |
| Extra: 016b84014e439dd5fcfabeb69242971a9d392db5678da472f21475a26f42dd34c2020900000002e49593ff00 | ||
1 output(s) for total of 34.644372563223 HMNY
| stealth address | amount | amount idx | tag |
| 00: 588c3f4f358f3f28ccfc485a598e81f9d3ac23b8f8fe4224d24f5772333f41f5 | 34.644372563223 | 10046 of 0 | <d5> |
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": 8170,
"vin": [ {
"gen": {
"height": 8110
}
}
],
"vout": [ {
"amount": 34644372563223,
"target": {
"tagged_key": {
"key": "588c3f4f358f3f28ccfc485a598e81f9d3ac23b8f8fe4224d24f5772333f41f5",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 107, 132, 1, 78, 67, 157, 213, 252, 250, 190, 182, 146, 66, 151, 26, 157, 57, 45, 181, 103, 141, 164, 114, 242, 20, 117, 162, 111, 66, 221, 52, 194, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}