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: d575c6de584eb6233c56551f6f1a2cd679794e944c803ddcdd0de3e52ab8bda0
Tx prefix hash: 2928daea8819c27c54d6094c6b02e2e38c1fb2f261a4f2671eecfbf228e1e827
Tx public key: 341438f762605cbe16aa74d874a81772b47f8f4010484d1e7cfda2a4c035c5b4
| Timestamp: 1780997064 | Timestamp [UTC]: 2026-06-09 09:24:24 | Age [y:d:h:m:s]: 00:000:05:24:31 |
| Block: 8366 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 276 | RingCT/type: yes/0 |
| Extra: 01341438f762605cbe16aa74d874a81772b47f8f4010484d1e7cfda2a4c035c5b4020900000001e49593ff00 | ||
1 output(s) for total of 34.627460478817 HMNY
| stealth address | amount | amount idx | tag |
| 00: 231ea3661aec4c0b96182b3b121297b787bfe419a6955a47a2482e9a928c5418 | 34.627460478817 | 10344 of 0 | <85> |
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": 8426,
"vin": [ {
"gen": {
"height": 8366
}
}
],
"vout": [ {
"amount": 34627460478817,
"target": {
"tagged_key": {
"key": "231ea3661aec4c0b96182b3b121297b787bfe419a6955a47a2482e9a928c5418",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 52, 20, 56, 247, 98, 96, 92, 190, 22, 170, 116, 216, 116, 168, 23, 114, 180, 127, 143, 64, 16, 72, 77, 30, 124, 253, 162, 164, 192, 53, 197, 180, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}