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: 5af834ac292196aa10db940ef36ea7a12e06cbb5c1cae2ff10e8a8384843bd49
Tx prefix hash: 454ce9540f88abe53eedac671dcc6e92b77518b062b2c311b9afcb6e0cb66ade
Tx public key: bea10ce53224f40b6c77843a22da5d884c28ba1e5e1c6d39c7c1b55ff9a7c787
| Timestamp: 1779434654 | Timestamp [UTC]: 2026-05-22 07:24:14 | Age [y:d:h:m:s]: 00:017:20:14:36 |
| Block: 96 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7844 | RingCT/type: yes/0 |
| Extra: 01bea10ce53224f40b6c77843a22da5d884c28ba1e5e1c6d39c7c1b55ff9a7c787020900000001a662ed0300 | ||
1 output(s) for total of 35.177997318351 HMNY
| stealth address | amount | amount idx | tag |
| 00: b47d5a49024af9a19b0b700fb8009e73c7457cb916282be017984c80693717e5 | 35.177997318351 | 92 of 0 | <86> |
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": 156,
"vin": [ {
"gen": {
"height": 96
}
}
],
"vout": [ {
"amount": 35177997318351,
"target": {
"tagged_key": {
"key": "b47d5a49024af9a19b0b700fb8009e73c7457cb916282be017984c80693717e5",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 190, 161, 12, 229, 50, 36, 244, 11, 108, 119, 132, 58, 34, 218, 93, 136, 76, 40, 186, 30, 94, 28, 109, 57, 199, 193, 181, 95, 249, 167, 199, 135, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}