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: 445c0b2fdc0042eb149daf8e963990ba2fdee81409daafecbfe135944dea08b7
Tx prefix hash: a746ca587a05ec73d2937e1b5f50bed0b2a2d5f6ceca5744ef3300178dc660e8
Tx public key: ab6257f573f192f96399e30480f5eff55d2869d3ad0cc50ceb6176f048b189b0
| Timestamp: 1780798985 | Timestamp [UTC]: 2026-06-07 02:23:05 | Age [y:d:h:m:s]: 00:010:05:42:16 |
| Block: 6804 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1941 | RingCT/type: yes/0 |
| Extra: 01ab6257f573f192f96399e30480f5eff55d2869d3ad0cc50ceb6176f048b189b0020900000001e49593ff00 | ||
1 output(s) for total of 34.730779259387 HMNY
| stealth address | amount | amount idx | tag |
| 00: fbc95dca14527b54a76b129ad74d25f4dd8ec0064cfa61d5e7d97624b8a4db86 | 34.730779259387 | 8402 of 0 | <7b> |
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": 6864,
"vin": [ {
"gen": {
"height": 6804
}
}
],
"vout": [ {
"amount": 34730779259387,
"target": {
"tagged_key": {
"key": "fbc95dca14527b54a76b129ad74d25f4dd8ec0064cfa61d5e7d97624b8a4db86",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 171, 98, 87, 245, 115, 241, 146, 249, 99, 153, 227, 4, 128, 245, 239, 245, 93, 40, 105, 211, 173, 12, 197, 12, 235, 97, 118, 240, 72, 177, 137, 176, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}