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: 1150b1bf06d4950c14bc1de91db40e5bbb758e6a42790068593499b546ad84c7
Tx prefix hash: 6d720a790bae76b3db1e2d31bc299dc3f4d20a38ad4f7e3cd23b342e073f0b35
Tx public key: 292a41036bb6c78d8c04a6632835d178726f1e07dc4737a89d5f3f65ef574099
| Timestamp: 1779949858 | Timestamp [UTC]: 2026-05-28 06:30:58 | Age [y:d:h:m:s]: 00:011:19:04:59 |
| Block: 3606 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4280 | RingCT/type: yes/0 |
| Extra: 01292a41036bb6c78d8c04a6632835d178726f1e07dc4737a89d5f3f65ef57409902090000000326697be300 | ||
1 output(s) for total of 34.943274247599 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1624dfb95950d30841f34336a3663f47fffef2ba183f2ba7053ab03a97e6e1d2 | 34.943274247599 | 4355 of 0 | <bb> |
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": 3666,
"vin": [ {
"gen": {
"height": 3606
}
}
],
"vout": [ {
"amount": 34943274247599,
"target": {
"tagged_key": {
"key": "1624dfb95950d30841f34336a3663f47fffef2ba183f2ba7053ab03a97e6e1d2",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 41, 42, 65, 3, 107, 182, 199, 141, 140, 4, 166, 99, 40, 53, 209, 120, 114, 111, 30, 7, 220, 71, 55, 168, 157, 95, 63, 101, 239, 87, 64, 153, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}