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: 0a3fe8931b3ef971c7aa29d6e08fe8d143f96a68f297b51a3c870b4b84eb3e5c
Tx prefix hash: bcddbfc69bfbe9da54f0df35e1dfeeeded4c87cb3c911c2f2cd57c2f0e6c31d9
Tx public key: eca2a8b89556664f9312a8ce9be67c605e1fd6a0b7e43c8d7e8c9d8b82cdc5d9
| Timestamp: 1780867496 | Timestamp [UTC]: 2026-06-07 21:24:56 | Age [y:d:h:m:s]: 00:001:04:11:01 |
| Block: 7683 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 203 | RingCT/type: yes/0 |
| Extra: 01eca2a8b89556664f9312a8ce9be67c605e1fd6a0b7e43c8d7e8c9d8b82cdc5d9020900000007e49593ff00 | ||
1 output(s) for total of 34.672599772103 HMNY
| stealth address | amount | amount idx | tag |
| 00: dcc5de834181e39c2cf4c1e73bd51d193480f4da2a1e32f42bb036c186385eba | 34.672599772103 | 9501 of 0 | <19> |
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": 7743,
"vin": [ {
"gen": {
"height": 7683
}
}
],
"vout": [ {
"amount": 34672599772103,
"target": {
"tagged_key": {
"key": "dcc5de834181e39c2cf4c1e73bd51d193480f4da2a1e32f42bb036c186385eba",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 236, 162, 168, 184, 149, 86, 102, 79, 147, 18, 168, 206, 155, 230, 124, 96, 94, 31, 214, 160, 183, 228, 60, 141, 126, 140, 157, 139, 130, 205, 197, 217, 2, 9, 0, 0, 0, 7, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}