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: dc42ddd20365f1b65ba3887b6981b5ba5da43c4706c60ca871eba5c17cf96237
Tx prefix hash: 58d18581fe08a1155d8c8bc55fa7c7493c36b215f85a84ad0997b742a02dbe45
Tx public key: 8a73d2f1f7cfa0a10c3130ff3808c277376e4d74eb99b1d5092abef92d85db14
| Timestamp: 1780131625 | Timestamp [UTC]: 2026-05-30 09:00:25 | Age [y:d:h:m:s]: 00:009:16:35:32 |
| Block: 4939 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2947 | RingCT/type: yes/0 |
| Extra: 018a73d2f1f7cfa0a10c3130ff3808c277376e4d74eb99b1d5092abef92d85db1402090000000126697be300 | ||
1 output(s) for total of 34.857966283582 HMNY
| stealth address | amount | amount idx | tag |
| 00: c300ced6fa52e130949eb1d159e0383909bfb6cbbf98a4ca65791c269c42e930 | 34.857966283582 | 6274 of 0 | <46> |
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": 4999,
"vin": [ {
"gen": {
"height": 4939
}
}
],
"vout": [ {
"amount": 34857966283582,
"target": {
"tagged_key": {
"key": "c300ced6fa52e130949eb1d159e0383909bfb6cbbf98a4ca65791c269c42e930",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 138, 115, 210, 241, 247, 207, 160, 161, 12, 49, 48, 255, 56, 8, 194, 119, 55, 110, 77, 116, 235, 153, 177, 213, 9, 42, 190, 249, 45, 133, 219, 20, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}