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: 4a7421159d5434b4b7660c05b53cd9f9d3633be2ebf52f0c0568dc9378251c4d
Tx prefix hash: 2c8316474e6d8b5b13625e3cba0dd391381098d900d6bd9407835d951514e765
Tx public key: d85e32833649356578ba0bc6479ae9dd8d45a91afddccb5bd4c0ab9b010cea74
| Timestamp: 1780751391 | Timestamp [UTC]: 2026-06-06 13:09:51 | Age [y:d:h:m:s]: 00:002:13:39:57 |
| Block: 6494 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1426 | RingCT/type: yes/0 |
| Extra: 01d85e32833649356578ba0bc6479ae9dd8d45a91afddccb5bd4c0ab9b010cea74020900000003e49593ff00 | ||
1 output(s) for total of 34.751320899634 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0ea58391b7891829604b4890d32883e9a9d3ad2b59c7b7b667b1e22cfba0219a | 34.751320899634 | 7991 of 0 | <9c> |
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": 6554,
"vin": [ {
"gen": {
"height": 6494
}
}
],
"vout": [ {
"amount": 34751320899634,
"target": {
"tagged_key": {
"key": "0ea58391b7891829604b4890d32883e9a9d3ad2b59c7b7b667b1e22cfba0219a",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 216, 94, 50, 131, 54, 73, 53, 101, 120, 186, 11, 198, 71, 154, 233, 221, 141, 69, 169, 26, 253, 220, 203, 91, 212, 192, 171, 155, 1, 12, 234, 116, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}